From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
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>, Magnus Hagander <magnus(at)hagander(dot)net>, Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: REVIEW: EXPLAIN and nfiltered |
Date: | 2011-01-21 02:08:10 |
Message-ID: | AANLkTimtLut7EXTpzWu2P1rmt2==LD0RG5_Cjqt6PErH@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 20, 2011 at 4:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jan 20, 2011 at 3:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> BTW, is it just me, or is the terminology "number filtered" pretty
>>> confusing/ambiguous in itself? It doesn't seem at all clear to me
>>> whether that's the number of rows passed by the filter condition or
>>> the number of rows rejected. Perhaps "nremoved" would be clearer.
>
>> I think filtered is pretty clear and like it... removed sounds like
>> you deleted something.
>
> Well, you did delete something, no? There are rows that aren't in the
> output that would have been there if not for the filter condition.
What I mean to say is that I fear that removed would give the
impression that some modification had been made to the database.
Perhaps that's silly, but it's what came to mind.
> And, btw, one person thinking it's clear doesn't make it so.
That's why I said "I think" rather than "Any fool should be able to see that".
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-01-21 02:12:30 | Re: One Role, Two Passwords |
Previous Message | Stephen Frost | 2011-01-21 02:07:14 | Re: One Role, Two Passwords |