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: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Abe Ingersoll <abe(at)abe(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: Fixing GIN for empty/null/full-scan cases
Date: 2011-01-18 22:04:16
Message-ID: 6459A15B-83B0-41D1-ADF3-4DEC6334C344@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-18 22:09:30 Re: Fixing GIN for empty/null/full-scan cases
Previous Message Tom Lane 2011-01-18 22:00:21 Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql