pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
To: arnaulist@andromeiberica.com
To: pgsql-admin@postgresql.org
Subject: Re: How do you upgrade for production servers?
Date: Fri, 29 Dec 2006 12:42:07 +0000
Message-ID: <45950D1F.6060900@mailnetwork.co.uk> (raw)
In-Reply-To: <459504E3.4050804@andromeiberica.com>
References: <459504E3.4050804@andromeiberica.com>

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




view thread (5+ messages)  latest in thread

Message-ID: <45950D1F.6060900@mailnetwork.co.uk>
Permalink:  ../45950D1F.6060900@mailnetwork.co.uk/
Also on:    postgresql.org/message-id/45950D1F.6060900@mailnetwork.co.uk

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: andy.shellam-lists@mailnetwork.co.uk, arnaulist@andromeiberica.com
  Subject: Re: How do you upgrade for production servers?
  In-Reply-To: <45950D1F.6060900@mailnetwork.co.uk>
  References: <459504E3.4050804@andromeiberica.com> <45950D1F.6060900@mailnetwork.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox