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

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-08 01:24:28
Message-ID: 13EE8904-90AA-438B-8792-B00743ED9B0D@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-08 01:29:10 Re: Fixing GIN for empty/null/full-scan cases
Previous Message Tom Lane 2011-01-08 01:20:33 Re: Remove pg_am.amindexnulls?