Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try
Date
Msg-id 603c8f070903241352q743e3180s38478013bc0dc7c6@mail.gmail.com
Whole thread Raw
Responses Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2009/3/24 Tom Lane <tgl@postgresql.org>:
> Implement "fastupdate" support for GIN indexes, in which we try to accumulate
> multiple index entries in a holding area before adding them to the main index
> structure.  This helps because bulk insert is (usually) significantly faster
> than retail insert for GIN.
>
> This patch also removes GIN support for amgettuple-style index scans.  The
> API defined for amgettuple is difficult to support with fastupdate, and
> the previously committed partial-match feature didn't really work with
> it either.  We might eventually figure a way to put back amgettuple
> support, but it won't happen for 8.4.
>
> catversion bumped because of change in GIN's pg_am entry, and because
> the format of GIN indexes changed on-disk (there's a metapage now,
> and possibly a pending list).

Will this break pg_migrator?

...Robert


pgsql-hackers by date:

Previous
From: Ben Ali Rachid
Date:
Subject: Re: Function C and INOUT parameters
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try