[Pkg-postgresql-public] Re: oldstable to stable upgrades

[Martin Pitt]

Hi Michelle,

Michelle Konzack [2007-04-24 16:43 +0200]:
> > If you have a fairly standard Sarge setup (data in
> > /var/lib/postgresql, no symlink hacks, etc.) it should work smoothly
> 
> Yeah.. I have had problems with this, since I have put my 6 PostgreSQL
> homes into /home/postgres-<flav>  because I run 6 PostgreSQL Servers
> on 6 different ports.
> 
> Only the first ${HOME} was reconized right.

Indeed, the transitional package does not go that far. It only
automatically upgrades what is automatically created by Sarge's
package maintainer scripts. Attempting to upgrade custom installations
would be mad and probably do more bad than good.

However, if you call pg_createcluster with an already existing
directory as --datadir, it is integrated into the postgresql-common
structure, so that you can use tools like pg_upgradecluster and
pg_lsclusters, get log rotation and cronjobs, and make pg_wrapper(1)
work properly.

Martin
-- 
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/20070502/102be242/attachment.pgp