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

From Tom Lane
Subject Re: Fixing GIN for empty/null/full-scan cases
Date
Msg-id 4049.1294445970@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fixing GIN for empty/null/full-scan cases  (David E. Wheeler <david@kineticode.com>)
Responses Re: Fixing GIN for empty/null/full-scan cases  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> We (PGX) actually have a client who could use this. Tom, if you have patches as you work on this (or, better, a
branchin a Git repo), I could do some testing on your client's code with it. It would involve converting from a GiST to
aGIN index and then seeing how well the queries fare. Would that be helpful to you?
 

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.
        regards, tom lane


pgsql-hackers by date:

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