Re: REVIEW: EXPLAIN and nfiltered

From: Florian Pflug <fgp(at)phlo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, robertmhaas(at)gmail(dot)com, marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi, depesz(at)depesz(dot)com, magnus(at)hagander(dot)net, pgsql-hackers(at)postgresql(dot)org, sfrost(at)snowman(dot)net
Subject: Re: REVIEW: EXPLAIN and nfiltered
Date: 2011-01-22 17:11:35
Message-ID: 25698CB8-B92F-41A9-9378-891243004AF2@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan22, 2011, at 17:55 , Tom Lane wrote:
> Reflecting on that, I'm inclined to suggest
>
> Bitmap Heap Scan ...
> Recheck Cond: blah blah
> Rows Removed by Recheck: 42
> Filter Cond: blah blah blah
> Rows Removed by Filter: 77
>
> or even more verbosely
>
> Bitmap Heap Scan ...
> Recheck Cond: blah blah
> Rows Removed by Recheck Cond: 42
> Filter Cond: blah blah blah
> Rows Removed by Filter Cond: 77
>
> ie repeat the label of the filtering condition exactly. This is looking
> pretty long, but from the viewpoint of vertical or horizontal space
> occupied by the printout, I doubt it matters.

+1. Repeating the label of the condition adds enough context to make
"Removed" unambiguous IMHO.

best regards,
Florian Pflug

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-22 17:12:06 Re: [COMMITTERS] pgsql: Move test_fsync to /contrib.
Previous Message David Fetter 2011-01-22 17:09:26 Re: REVIEW: EXPLAIN and nfiltered