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

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try
Date
Msg-id 8662.1237929364@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> 2009/3/24 Tom Lane <tgl@postgresql.org>:
>> 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?

No worse than it's already broken by hash indexes.  I would imagine
the strategy will just be to force a REINDEX on any non-btree indexes.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try
Next
From: Robert Lor
Date:
Subject: Re: DTrace probes broken in HEAD on Solaris?