[Pkg-postgresql-private] System for managing multiple postmasters?

Martin Pitt martin@piware.de
Wed, 15 Oct 2003 19:25:05 +0200


--EVF5PPMfhYS0aIcm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi again!

On 2003-10-15 15:04 +0200, Martin Pitt wrote:
> I would pg_dumpall my current db, purge everything, install the new
> psql version and feed back the dump. As a migration strategy on SQL
> level (as opposed to binary), this method would take much longer, but
> is certainly far more robust. So if binary updating isn't possible or
> reliable, then why we don't just offer an automated way of doing this
> source-level conversion?=20

Please forget about the binary update, this of course was crap. But
nevertheless the problem persists. I just tried upgrading from 7.3.4
(sid) to 7.4.0-beta4 (alioth) and upgrading failed:

-------------- snip ------------------
Attempting PostgreSQL database upgrade; the time taken will depend on the
size of your database(s).
Sorry; the automatic database upgrade failed.

-------------- snip ------------------
root@donald:/mm/pg# /var/lib/postgres/dumpall/7.3/pg_dumpall
/var/lib/postgres/dumpall/7.3/pg_dumpall: error while loading shared librar=
ies:
libkrb5.so.17: cannot open shared object file: No such file or directory
-------------- snip ------------------

The pg_dumpall from 7.3 doesn't work any longer because of the changed
libkrb5. I reinstalled 7.3.4 then, dumped the database with its
pg_dumpall, then purged and reinstalled 7.4.0beta and fed back the
dump which worked fine.

Thus, it would be nice if during an upgrade the old version was
responsible for dumping the database (i. e. do it in its prerm) and
the new version for restoring it. By now, the new db does the dump
which seems far less reliable.=20

Splitting the task had the disadvantage that it does not fit into a
single script anymore, but at least in my case it had worked.

What do you think?

Martin
--=20
Martin Pitt
home:  www.piware.de
eMail: martin@piware.de

--EVF5PPMfhYS0aIcm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/jYLxDecnbV4Fd/IRAiFnAKDr8lFuQAmOgyTcb1a9wZA6KgbfcgCfZhO7
QrcJA7Q5DSyQM7tiyGQLUB4=
=abe3
-----END PGP SIGNATURE-----

--EVF5PPMfhYS0aIcm--