Fix comment related to calculation location of total_table_pages

michaelpq · michaelpq · commit 6ea95166a0f1 · 2019-02-13T16:31:20.000+09:00
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
diff --git 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

Original file line number	Diff line number	Diff line change
`@@ -815,7 +815,7 @@ extract_nonindex_conditions(List qual_clauses, List indexclauses)`
`815`	`815`	`* product rather than calculating it here. "pages" is the number of pages`
`816`	`816`	`* in the object under consideration (either an index or a table).`
`817`	`817`	`* "index_pages" is the amount to add to the total table space, which was`
`818`		`- * computed for us by query_planner.`
	`818`	`+ * computed for us by make_one_rel.`
`819`	`819`	`*`
`820`	`820`	`* Caller is expected to have ensured that tuples_fetched is greater than zero`
`821`	`821`	`* and rounded to integer (see clamp_row_est). The result will likewise be`