Tom Lane wrote: > Robert Haas <[email protected]> writes: > > 2009/3/24 Tom Lane <[email protected]>: > >> 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.
Agreed. -- Bruce Momjian <[email protected]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
