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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@kineticode.com>
Cc: pgsql-hackers@postgresql.org
Date: 2011-01-08T00:19:30Z
Lists: 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 branch in a Git repo), I could do some testing on your client's code with it. It would involve converting from a GiST to a GIN 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