From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Parkyns <andrew.parkyns@microgen.co.uk>
Cc: pgsql-ports@postgresql.org
Subject: Re: PostgreSQL Upgrade recommendations
Date: Mon, 09 Aug 2004 10:53:28 -0400
Message-ID: <14719.1092063208@sss.pgh.pa.us> (raw)
In-Reply-To: <auto-000004324498@microgen.co.uk>
References: <auto-000004324498@microgen.co.uk>
"Andrew Parkyns" <andrew.parkyns@microgen.co.uk> writes:
> We have a PostgreSQL 7.2.1 server on Linux RHL 9 Enterprise / Intel port.
> * I want an up-to-date upgrade version, not too new and unstable.
> Which one? 7.4.x? Wait for 7.5? I don't want to do this too often so I would
> like to space major upgrade intervals by at least 12 months if possible.
7.4.latest would be your best bet. Given the degree of conservatism you
are expressing, you will not want to move onto the 8.0.* (nee 7.5)
series for about a year anyway.
> * Any really pressing reasons to move off 7.2.x ? Nasty bugs not
> patches until later versions?
There are *really* good reasons not to be running 7.2.1 --- see the
release notes for the later 7.2.* releases. You should most certainly
update to 7.2.4 (or whatever the last of that series was) ASAP. Moving
to 7.3.* or 7.4.* would entail a dump/reload as well as posing some
possible compatibility risks, so that's a bigger jump and you need to
think harder about if it's worth it to you.
In general, whatever release series you're using, you should be at the
latest release in the series. We only do bug fixes in minor releases,
and usually only bother for fairly serious bugs.
> * Reasons of performance / functionality?
Generally the performance and functionality both get better with every
release. But it's impossible to say at this level of detail whether
7.3 or 7.4 will have anything especially attractive for your particular
situation.
regards, tom lane
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: tgl@sss.pgh.pa.us, andrew.parkyns@microgen.co.uk, pgsql-ports@postgresql.org
Subject: Re: PostgreSQL Upgrade recommendations
In-Reply-To: <14719.1092063208@sss.pgh.pa.us>
References: <auto-000004324498@microgen.co.uk> <14719.1092063208@sss.pgh.pa.us>
* 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