Amit Khandekar wrote:
> On 25 November 2013 13:37, Etsuro Fujita <fujita.ets...@lab.ntt.co.jp> wrote:
>> So, my question is, we should show the number of exact/lossy pages in a
>> TIDBitmap, not the number of these pages that has been fetched in the bitmap
>> heap scan?
> Yes, I agree that rather than looking at the bitmap heap scan to track the
> number of pages, we should look somewhere in the underlying index scan. Yes,
> we should get a constant number of index pages regardless of the actual
> parent table rows. I can see that btgetbitmap() adds all the tuples into the
> bitmap, so somewhere below under btgetbitmap() might be the right place to
> track. Somewhere in tbm_create_pagetable(), but not sure.
Thank you for the comment!
I agree with you. I'll modify the patch to show 1) the number of the
exact/lossy pages in a TIDBitmap by examining the underlying index scan, not
the number of these pages that have been fetched in the bitmap heap scan, and
2) the memory requirement.
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: