Re: REVIEW: EXPLAIN and nfiltered - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: REVIEW: EXPLAIN and nfiltered
Date
Msg-id 25698CB8-B92F-41A9-9378-891243004AF2@phlo.org
Whole thread Raw
In response to Re: REVIEW: EXPLAIN and nfiltered  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: REVIEW: EXPLAIN and nfiltered  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: REVIEW: EXPLAIN and nfiltered
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Move test_fsync to /contrib.