Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier2019-02-13 07:31:20 +0000
committerMichael Paquier2019-02-13 07:31:20 +0000
commit6ea95166a0f19ca0363b9c868e676b10365edec9 (patch)
tree145ee99853937131ec55b55a1adf6ec13793ac79
parent7215efdc005e694ec93678a6203dbfc714d12809 (diff)
Fix comment related to calculation location of total_table_pages
As of commit c6e4133, the calculation happens in make_one_rel() and not query_planner(). Author: Amit Langote Discussion: https://postgr.es/m/c7a04a90-42e6-28a4-811a-a7e352831ba1@lab.ntt.co.jp
-rw-r--r--src/backend/optimizer/path/costsize.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/optimizer/path/costsize.c b/src/backend/optimizer/path/costsize.c
index beee50ec135..4b9be13f08e 100644
--- a/src/backend/optimizer/path/costsize.c
+++ b/src/backend/optimizer/path/costsize.c
@@ -815,7 +815,7 @@ extract_nonindex_conditions(List *qual_clauses, List *indexclauses)
* product rather than calculating it here. "pages" is the number of pages
* in the object under consideration (either an index or a table).
* "index_pages" is the amount to add to the total table space, which was
- * computed for us by query_planner.
+ * computed for us by make_one_rel.
*
* Caller is expected to have ensured that tuples_fetched is greater than zero
* and rounded to integer (see clamp_row_est). The result will likewise be