pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Tsirkin Evgeny <tsurkin@mail.jct.ac.il>
Cc: pgsql-admin@postgresql.org
Subject: Re: upgrading postgresql
Date: Wed, 15 Dec 2004 10:20:00 -0600
Message-ID: <1103127600.22049.40.camel@state.g2switchworks.com> (raw)
In-Reply-To: <41C00963.7090904@mail.jct.ac.il>
References: <41C00963.7090904@mail.jct.ac.il>

On Wed, 2004-12-15 at 03:52, Tsirkin Evgeny wrote:
> Hi all!
> We are currently running a 7.3.4 backed and planning to upgrade.
> However we can't do to much/at all changes in the applications using the db.
> So the question is to what version to upgrade :
> what is the best release from the 7.3.* ?
> would the upgrade to 7.4.* require serious changes in the applications , 
> if not what is the
> best release of the 7.4.*?

The best version of any major release is the latest minor version.  As
of this writing, the latest minor version of the 7.3 branch is 7.3.8,
and the latest minor version of the 7.4 branch is 7.4.6.

Upgrades from one minor version to another (i.e. 7.3.4 to 7.3.8) are
usually painless and simple:

-- Always backup ahead of time just in case.
-- Stop the server.
-- Upgrade PostgreSQL.
-- Start server.

No changes to client side apps should be necessary.

For upgrades from one major version to the next, you'll need to:

-- pg_dump all databases in the cluster.  (optionally, also backup the
files in the $PGDATA directory)
-- Clean out the $PGDATA directory (keep a copy of your pg_hba.conf and
postgresql.conf for reference)
-- Uninstall old version of PostgreSQL
-- Install new version of PostgreSQL
-- initdb with the proper locale
-- edit your pg_hba.conf and postgresql.conf
-- start database
-- restore from backups.

I'd recommend a test run of the major upgrade procedures you're planning
on doing on a backup machine in case you run into some problems.  Use of
a replication engine, like Slony as well as pgpool can allow you to
seamlessly upgrade your installation while it stays online.  I'd
practice this too on a backup system before going after the live
servers.



view thread (6+ messages)  latest in thread

Message-ID: <1103127600.22049.40.camel@state.g2switchworks.com>
Permalink:  ../1103127600.22049.40.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1103127600.22049.40.camel@state.g2switchworks.com

 · 

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: smarlowe@g2switchworks.com, tsurkin@mail.jct.ac.il
  Subject: Re: upgrading postgresql
  In-Reply-To: <1103127600.22049.40.camel@state.g2switchworks.com>
  References: <41C00963.7090904@mail.jct.ac.il> <1103127600.22049.40.camel@state.g2switchworks.com>

* 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