2009/3/24 Tom Lane <tgl(at)postgresql(dot)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

In response to

• pgsql: Implement "fastupdate" support for GIN indexes, in which we try at 2009-03-24 20:17:18 from Tom Lane

Responses

• Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try at 2009-03-24 21:16:04 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2009-03-24 21:16:04
	Subject: Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try
Previous:	From: Tom Lane	Date: 2009-03-24 20:18:42
	Subject: Re: GIN fast insert

pgsql-committers by date

Next:	From: Tom Lane	Date: 2009-03-24 21:12:56
	Subject: pgsql: Fix stupid parenthesization mistake.
Previous:	From: Tom Lane	Date: 2009-03-24 20:17:18
	Subject: pgsql: Implement "fastupdate" support for GIN indexes, in which we try