Re: PostgreSQL Upgrade recommendations - Mailing list pgsql-ports

From Merlin Moncure
Subject Re: PostgreSQL Upgrade recommendations
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB34101AF2A@Herge.rcsinc.local
Whole thread Raw
In response to PostgreSQL Upgrade recommendations  ("Andrew Parkyns" <andrew.parkyns@microgen.co.uk>)
List pgsql-ports
We have a PostgreSQL 7.2.1 server on Linux RHL 9 Enterprise / Intel
port.
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.5 has a lot of new stuff in it.  If that new stuff applies to you then
go for it, otherwise might be smart to wait for 8.1 (7.5 == 8.0).  If
you don't care about win32, the next biggest thing is probably
savepoints.  If you are the conservative type, I would not target an 8.0
deployment earlier than Jan 1. 2005.

* Any really pressing reasons to move off 7.2.x ? Nasty bugs not patches
until later versions?

Yes, 7.4 got a lot of improvements to the query optimizer, a major
protocol overhaul, and takes better care of your data in crash
scenarios, not to mention all the 7.3 stuff.

* 3rd party software Incompatibility issues?

Possibly, in a few minor cases the sql commands are not backwards
compatible.  However, the protocols are.  If you have a lot of
integration, there might be some problems.

* Reasons of performance / functionality?

Yes, postgres just keeps getting better and better.  Each major version
brings a huge amount of functionality and power.

Merlin

pgsql-ports by date:

Previous
From: "Andrew Parkyns"
Date:
Subject: PostgreSQL Upgrade recommendations
Next
From: Robert Treat
Date:
Subject: Re: PostgreSQL Upgrade recommendations