Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 2009/3/24 Tom Lane <tgl(at)postgresql(dot)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

In response to

• Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try at 2009-03-24 20:52:22 from Robert Haas

Responses

• Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try at 2009-03-26 01:34:18 from Bruce Momjian

pgsql-hackers by date

Next:	From: Robert Lor	Date: 2009-03-24 21:31:43
	Subject: Re: DTrace probes broken in HEAD on Solaris?
Previous:	From: Robert Haas	Date: 2009-03-24 20:52:22
	Subject: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try

pgsql-committers by date

Next:	From: User Hinoue	Date: 2009-03-24 21:38:46
	Subject: psqlodbc - psqlodbc: Add a textbox to setup dialog to change the
Previous:	From: Tom Lane	Date: 2009-03-24 21:12:56
	Subject: pgsql: Fix stupid parenthesization mistake.