[Pkg-postgresql-public] oldstable to stable upgrades

Martin Pitt mpitt at debian.org
Tue Apr 17 06:45:20 UTC 2007

Hi Wookey,

Wookey [2007-04-16 23:02 +0100]:
> If I just do a standard upgrade do I need to worry about the fact that
> stable has 7.5? I note a postgres-7.4 package. Can I have both
> installed and control with alternatives, or is it a matter of choosing
> one or the other.

7.5 is a 'fake' version. Etch's 'postgresql' is a transitional package
that has some bits to move Sarge's data of postgresql into the new
multiversion/multicluster architecture of Etch's postgresql-<version>
packages. Thus after the upgrade you will have postgresql-7.4
installed, just as in Sarge, so that the actual db data will not be
touched during the upgrade. 

You can later install postgresql-8.1 and conveniently migrate the 7.4
data to 8.1 with pg_upgradecluster (see its manpage), test the 8.1
cluster, and have the security of having your original 7.4 instance as
a rollback.

> I was planning to try an upgrade in a chroot and see how that worked -
> is that excessive?

If you have a fairly standard Sarge setup (data in
/var/lib/postgresql, no symlink hacks, etc.) it should work smoothly
(I had an automated test for that), but of course testing it before
can never hurt. The Sarge->Etch update still has potential for
breakage, with the new architecture in Etch upgrades will be much
safer in the future.


Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20070417/6e331305/attachment.pgp

More information about the Pkg-postgresql-public mailing list