From 6ea95166a0f19ca0363b9c868e676b10365edec9 Mon Sep 17 00:00:00 2001 From: Michael Paquier Date: Wed, 13 Feb 2019 16:31:20 +0900 Subject: [PATCH] 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 --- src/backend/optimizer/path/costsize.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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