Re: GIN fast insert - Mailing list pgsql-hackers

From Robert Haas
Subject Re: GIN fast insert
Date
Msg-id 603c8f070902121052n36582b02jaf2b58eb1e3bd71a@mail.gmail.com
Whole thread Raw
In response to Re: GIN fast insert  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GIN fast insert
List pgsql-hackers
On Thu, Feb 12, 2009 at 1:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Teodor Sigaev <teodor@sigaev.ru> writes:
>>> What did you think of the idea of simply abandoning support for
>>> conventional indexscans in GIN?
>
>> I don't like this idea because it forbids conventional indexscans even with
>> fastupdate=off.
>
> So?  Barring some evidence that there's a significant performance win
> from a conventional indexscan, this is a weak argument.  AFAICS the only
> significant advantage of the conventional API is to support ordered
> scans, and GIN doesn't do that anyway.

Wouldn't it force you to recheck all tuples on the page, instead of
just rechecking the one of interest?

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_migrator and handling dropped columns
Next
From: Cédric Villemain
Date:
Subject: Re: pg_restore --multi-thread