If upgrading between minor versions in the same series (e.g. 8.1.3 -
8.1.5) you can simply use the same data directory.
However, if the major version changes (e.g. 8.1.x - 8.2.x), you must:
1. Dump the databases from your old server (preferably using the new
version client, I believe) while your old server is still running
2. Stop your old version
3. Start your new version
4. Restore the backup into your new version
For the minimum downtime, the best thing to do is get the 2 servers
running together (e.g. run your new version on port 5433) - then dump
your old database, stop your old server (so no updates can get in after
your backup), restore the backup into the new server, and restart your
new server on port 5432. It all depends on how big your databases are,
and the length of time it'll take to restore your backup.
Happy New Year to you too.
Andy.
Arnau wrote:
> Hi all,
>
> This is a general question about which procedure you follow when you
> upgrade your productions servers. Let's say we have a server running
> and older version and I want to install the latest version on the same
> server. Do you install slony? do you dump all the databases, install
> the latest version and after you restore? any other procedure? I'd
> like to have my production server down as less time as possible.
>
>
> Thank you very much and have a great new year :D
--
Andy Shellam
NetServe Support Team
the Mail Network
"an alternative in a standardised world"
p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834