Re: EXPLAIN and nfiltered - Mailing list pgsql-hackers

From Tom Lane
Subject Re: EXPLAIN and nfiltered
Date
Msg-id 1321.1290097569@sss.pgh.pa.us
Whole thread Raw
In response to EXPLAIN and nfiltered  (Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi>)
Responses Re: EXPLAIN and nfiltered
List pgsql-hackers
Marko Tiikkaja <marko.tiikkaja@cs.helsinki.fi> writes:
> Here's a patch for showing in EXPLAIN ANALYZE the number of rows a plan 
> qual filtered from a node's input.

I don't like this a whole lot.  It's unclear what "filtered" means,
or why it's worth expending precious EXPLAIN ANALYZE output space for.

Also, you've not implemented it for any except scan nodes; and I
think it's not going to be entirely well-defined for join nodes,
since it's somewhat arbitrary which conditions are considered part
of the join qual versus the filter.  (That problem will get worse
not better with the planned generalization of inner indexscans,
since there may be join quals in scan nodes.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: final patch - plpgsql: for-in-array
Next
From: Marko Tiikkaja
Date:
Subject: Re: EXPLAIN and nfiltered