| From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | depesz(at)depesz(dot)com, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: REVIEW: EXPLAIN and nfiltered |
| Date: | 2011-01-20 23:23:45 |
| Message-ID: | 4D38C401.4070808@cs.helsinki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/20/2011 12:47 PM, Tom Lane wrote:
> So the line I'm thinking we should pursue is to visually associate the
> new counter with the filter condition, either like
>
> Filter Cond: (x> 42) (nfiltered = 123)
>
> or
>
> Filter Cond: (x> 42)
> Rows Filtered: 123
I'd prefer the latter. Sometimes the Filter Cond is very complex and
finding the nfiltered information would be easier if it always had its
own row.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2011-01-20 23:26:49 | Re: SSI and Hot Standby |
| Previous Message | Kevin Grittner | 2011-01-20 23:22:49 | Re: SSI and Hot Standby |