Re: No exact/lossy block information in EXPLAIN ANALYZE for a bitmap heap scan

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: No exact/lossy block information in EXPLAIN ANALYZE for a bitmap heap scan
Date: 2014-07-14 12:01:34
Message-ID: CAHGQGwFH8JFvGgzaNLYVqov25Je3048wwmJ5XhMLyRugcRjeyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 11, 2014 at 7:21 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Fri, Jul 11, 2014 at 5:45 PM, Etsuro Fujita
> <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> I've noticed that EXPLAIN ANALYZE shows no information on exact/lossy
>> blocks for a bitmap heap scan when both the numbers of exact/lossy pages
>> retrieved by the node are zero. Such an example is shown below. I
>> think it would be better to suppress the 'Heap Blocks' line in that
>> case, based on the same idea of the 'Buffers' line. Patch attached.
>
> The patch looks good to me. Barring any objection, I will commit this both
> in HEAD and 9.4.

Committed!

Regards,

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2014-07-14 12:09:56 Re: Re: issue log message to suggest VACUUM FULL if a table is nearly empty
Previous Message Tom Lane 2014-07-14 11:55:34 Re: Re: issue log message to suggest VACUUM FULL if a table is nearly empty