From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
---|---|
To: | Martin Spinassi <martins(dot)listz(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Replication for migration |
Date: | 2009-05-14 13:59:40 |
Message-ID: | 20090514135940.GS28923@it.is.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Spinassi | 2009-05-14 14:20:15 | Re: Replication for migration |
Previous Message | Martin Spinassi | 2009-05-14 13:57:26 | Replication for migration |