| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Marko Tiikkaja <marko(dot)tiikkaja(at)2ndquadrant(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: EXPLAIN and nfiltered, take two |
| Date: | 2011-09-22 06:28:42 |
| Message-ID: | 4E7AD59A.7080702@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.09.2011 07:51, Tom Lane wrote:
> Here's a revised version of the patch that behaves in a way that seems
> reasonable to me, in particular it suppresses zero filter-count rows in
> text mode. I've not done anything yet about the documentation.
I haven't been following this closely, so sorry if this has already been
discussed, but:
I find it a bit strange to print the number of lines filtered out. I
think that's the only place where we would print a "negative" like that,
everywhere else we print the number of lines let through a node. How
about printing the number of lines that enter the filter, instead?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-22 06:41:12 | Re: EXPLAIN and nfiltered, take two |
| Previous Message | Jeff Davis | 2011-09-22 06:01:22 | Re: Range Types - typo + NULL string constructor |