Postgres Pro
Downloads
Home   >   mailing lists

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 6459A15B-83B0-41D1-ADF3-4DEC6334C344@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>)
List pgsql-hackers
Tree view 
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

Best,

David

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql
Next
From: Tom Lane
Date:
Subject: Re: Fixing GIN for empty/null/full-scan cases