Re: pg_upgrade - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade
Date
Msg-id 200201110216.g0B2GP221131@candle.pha.pa.us
Whole thread Raw
In response to pg_upgrade  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_upgrade  (Peter Eisentraut <peter_e@gmx.net>)
Re: pg_upgrade  (Daniel Kalchev <daniel@digsys.bg>)
List pgsql-hackers
Bruce Momjian wrote:
> Tom asked about pg_upgrade as part of our initdb for timezone.
> 
> I have made some improvements to pg_upgrade in CVS and have successfully
> migrated a regression database from a 7.2 to another 7.2 database using
> it.  (At least the tables show some data;  very light testing.)
> 
> pg_upgrade is still disabled in CVS, it doesn't install, and there is no
> manual page so it is still an unused command. I have made the commit so
> people can review where I have gone and make comments.
> 
> To test it, you have to find the line that says 7.2 and remove the '#'
> comment.  This is for testing purposes only, so far.

Status report:  I have completed all the steps necessary for pg_upgrade
to work for 7.1->7.2 and for 7.2->7.2 databases.  I will run tests
tomorrow, and once I am sure it works, I will ask others to test.

I will not enable it until everyone agrees.  Are there people interested
in this tool being in 7.2, or who are against this tool being in 7.2?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Sequence rows need to have FrozenTransactionId
Next
From: Joe Conway
Date:
Subject: Re: pg_upgrade