From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | obsolete comment above index_pages_fetched |
Date: | 2019-02-13 04:57:09 |
Message-ID: | c7a04a90-42e6-28a4-811a-a7e352831ba1@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I think the following commit:
commit c6e4133fae1fde93769197379ffcc2b379845113
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Wed Nov 7 12:12:56 2018 -0500
Postpone calculating total_table_pages until after pruning/exclusion.
...
obsoleted a sentence in the comment above index_pages_fetched(), which says:
* "index_pages" is the amount to add to the total table space, which was
* computed for us by query_planner.
total_table_pages is computed by make_one_rel as of the aforementioned
commit. Attached fixes this.
Thanks,
Amit
Attachment | Content-Type | Size |
---|---|---|
index_pages_fetched-comment-fix.patch | text/plain | 759 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuro Yamada | 2019-02-13 05:03:46 | Re: monitoring CREATE INDEX [CONCURRENTLY] |
Previous Message | Amit Langote | 2019-02-13 04:31:53 | Re: monitoring CREATE INDEX [CONCURRENTLY] |