From: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: lock database share |
Date: | 2012-11-05 18:11:09 |
Message-ID: | 1651975.mBcOjN1F8a@skynet.simkin.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday, November 05, 2012 05:15:41 AM salah jubeh wrote:
> Hello,
>
> I have the following scenario, I would like to upgrade a database server
> from 8.3 to 9.1. The upgrade includes also a hardware upgrade.
>
>
> I would like to have the following
>
> 1. Make sure that the upgraded server and the old server have the same
> snapshot of data. 2. Make sure that the old server data is accessible for
> read only after taking the data snapshot until making the new server alive
> and tested
>
>
> The lock database command is not yet implemented, so what are the ways to
> hack this command. Also, I need to make sure that the server is down for
> very short time, so is there a better way than using pg_dump and pg_restore
> for different database server versions ?
>
> Regards
Using Slony to assist in your migration will meet all your requirements:
You should read the documentation thoroughly. And try everything out on test
machines before doing it to your production servers.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Serodio (lists) | 2012-11-05 18:19:16 | Re: [GENERAL] Error registering at postgresql.org |
Previous Message | Stephen Woodbridge | 2012-11-05 17:55:15 | Re: Problem with heap_form_tuple error |