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: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-08 01:29:10
Message-ID: 1826.1294450150@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 7, 2011, at 4:19 PM, Tom Lane wrote:
>> Well, actually, I just committed it. If you want to test, feel free.
>> Note that right now only the anyarray && <@ @> operators are genuinely
>> fixed ... I plan to hack on tsearch and contrib pretty soon though.

> Hrm, the queries I wrote for this sort of thing use intarray:

> WHERE blah @@ '(12|14)'::query_int

> That's not done yet though, right?

Right. Maybe sometime this weekend.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-01-08 01:59:01 pgbench to the MAXINT
Previous Message David E. Wheeler 2011-01-08 01:24:28 Re: Fixing GIN for empty/null/full-scan cases