Bruce Momjian wrote:
> pg_migrator (not pg_upgrade) has been used by many people to migrate
> from 8.3 to 8.4. I just helped someone yesterday with a migration.
> pg_migrator threw an error because they had reindexed pg_largeobject,
> and pg_migrator was not prepared to handle that. They also had an old
> cluster with a higher autovacuum_freeze_max_age than the new cluster,
> causing autovacuum freeze to run during the upgrade and remove clog
> files. These are unusual cases, so I assume there are many people who
> successfully use pg_migrator that I never hear from.
>
> Both of these issues are fixed in pg_migrator 8.4.6, released yesterday.
> I also talked to Alvaro about using fixed oids to remove these migration
> restrictions in 8.5:
>
> o a user-defined composite data type
> o a user-defined array data type
> o a user-defined enum data type
>
> So, pg_migrator is a work in progress. It current requires migration
> testing and should be used by experienced Postgres users. Someday
> pg_migrator will be easier to use and more reliable.
Oh, and pg_migrator 8.4.6 works for migrations from 8.4 to 8.5 CVS.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
