Re: pg_migrator issue with contrib

Grzegorz Jaskiewicz wrote:
>
> On 7 Jun 2009, at 03:27, Bruce Momjian wrote:
>
> > Grzegorz Jaskiewicz wrote:
> >>
> >> On 6 Jun 2009, at 19:50, Tom Lane wrote:
> >>> We have five days.
> >>>
> >>> I don't think we need testing, per se. The first step should be to
> >>> diff
> >>> the 8.3 and 8.4 versions of the various contrib .sql.in files and
> >>> determine what changed. Any module whose .sql.in file hasn't
> >>> changed
> >>> is definitely safe.
> >>
> >> I can tell you already that dblink has changed, and I had to drop it
> >> before migration, otherwise everything went fine. Migration of 57GB
> >> data in place took about 1 minute.
> >
> > The good news is that the INSTALL instructions where clear enough for
> > the tester to understand that uninstalling dblink from the old cluster
> > and reinstalling it in the new cluster would work.
> Yes, but I forgot about one database, and had to do it all over again,
> luckily I first tested it without --link...

Any failure would have allowed you to revert to the old server. It is
only when you _start_ the new server that the old server cannot be used;
I have clarified the INSTALL file on that point.

If you use linking, the migration will be much faster (no data copying),
but you will no longer be able to access your old cluster once you start
the new cluster after the upgrade.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +