From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/planner-stats.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/planner-stats.html') diff --git a/doc/src/sgml/html/planner-stats.html b/doc/src/sgml/html/planner-stats.html index 7cff365..96eb821 100644 --- a/doc/src/sgml/html/planner-stats.html +++ b/doc/src/sgml/html/planner-stats.html @@ -1,5 +1,5 @@ -14.2. Statistics Used by the Planner
14.2. Statistics Used by the Planner
Prev UpChapter 14. Performance TipsHome Next

14.2. Statistics Used by the Planner

14.2.1. Single-Column Statistics
14.2.2. Extended Statistics

14.2.1. Single-Column Statistics

+14.2. Statistics Used by the Planner

14.2. Statistics Used by the Planner
Prev UpChapter 14. Performance TipsHome Next

14.2. Statistics Used by the Planner

14.2.1. Single-Column Statistics
14.2.2. Extended Statistics

14.2.1. Single-Column Statistics

As we saw in the previous section, the query planner needs to estimate the number of rows retrieved by a query in order to make good choices of query plans. This section provides a quick look at the statistics @@ -333,4 +333,4 @@ SELECT m.* FROM pg_statistic_ext join pg_statistic_ext_data on (oid = stxoid), and for which misestimation of the number of groups is resulting in bad plans. Otherwise, the ANALYZE and planning cycles are just wasted. -

Prev Up Next
14.1. Using EXPLAIN Home 14.3. Controlling the Planner with Explicit JOIN Clauses
\ No newline at end of file +

Prev Up Next
14.1. Using EXPLAIN Home 14.3. Controlling the Planner with Explicit JOIN Clauses
\ No newline at end of file -- cgit v1.2.3