From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)postgresql(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try |
Date: | 2009-03-24 20:52:22 |
Message-ID: | 603c8f070903241352q743e3180s38478013bc0dc7c6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-24 21:12:56 | pgsql: Fix stupid parenthesization mistake. |
Previous Message | Tom Lane | 2009-03-24 20:17:18 | pgsql: Implement "fastupdate" support for GIN indexes, in which we try |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-24 21:16:04 | Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try |
Previous Message | Tom Lane | 2009-03-24 20:18:42 | Re: GIN fast insert |