"David E. Wheeler" <david@kineticode.com> writes:
> On Jan 18, 2011, at 1:39 PM, Tom Lane wrote:
>> At the moment my opinion is that gist__int_ops is too broken to be
>> usable, and it's also too uncommented to be fixable by anyone other
>> than the original author.
> That seems to jibe with your comments from last year:
> http://archives.postgresql.org/pgsql-performance/2009-03/msg00265.php
Well, based on what I saw just now, I believe there are one or more
actual bugs in there, not just that it's straining the design capacity
of the opclass. I think the "lossy" aspect isn't working at all.
regards, tom lane