On Thu, May 14, 2009 at 10:57:26AM -0300, Martin Spinassi wrote: > Hi list! > > I've to do a migration of postgresql from version 8.2 to 8.3 in one > server. The problem I see here is, to avoid data loss (people still > using the web site that uses postgres), I'll need to stop postgres 8.2, > make a pg_dumpall, and then restore that information in 8.3. > Taking some considerations, like database size, server, etc. I estimate > that it will be at least 30 minutes of downtime, and that's pretty much > time. > > I've thinking in the possibility of doing some kind of master/slave with > both versions (I must change the default port in one of them, as > everything must happen on a single machine), and find some useful links > like: > > http://wiki.postgresql.org/wiki/Replication%2C_Clustering% > 2C_and_Connection_Pooling > http://momjian.us/main/writings/pgsql/replication.pdf > > > I'd love to read some experiences or advices, since I haven't done it > before. Also if you have some link o document that you think I must > read, it'll be welcomed. > > > Thanks to all. > > > Mart??n > I used Slony replication to upgrade a database from 8.2 -> 8.3 and it worked quite well. You will need an outage to change the master to the 8.3 database and re-point your apps, but if scripted, that is minimal. Cheers, Ken -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
