Re: Fixing GIN for empty/null/full-scan cases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Abe Ingersoll <abe(at)abe(dot)us>
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-18 23:08:03
Message-ID: 6112.1295392083@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On Jan 18, 2011, at 1:58 PM, Tom Lane wrote:
>> I'm noticing also that I get different rowcounts than you do, although
>> possibly that has something to do with the partial-index conditions,
>> which I'm not trying to duplicate here (all rows in my table pass those
>> two tests).

> Shall I send you data with the other two columns?:

No, I see no reason to think that has much to do with it. I'm wondering
if your table is itself a bit bloated ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-01-18 23:09:27 Re: test_fsync label adjustments
Previous Message Tom Lane 2011-01-18 23:06:09 Re: test_fsync label adjustments