Re: Fixing GIN for empty/null/full-scan cases - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Fixing GIN for empty/null/full-scan cases
Date
Msg-id 13EE8904-90AA-438B-8792-B00743ED9B0D@kineticode.com
Whole thread Raw
In response to Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
contrib/intarray (was Re: Fixing GIN for empty/null/full-scan cases)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Fixing GIN for empty/null/full-scan cases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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?

Best,

David




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Remove pg_am.amindexnulls?
Next
From: Tom Lane
Date:
Subject: Re: Fixing GIN for empty/null/full-scan cases