Could powerpc peopls please look at this bug report; I am unable to do
anything about it without a suitable machine.
Explanation:
When postgresql is upgraded with a new upstream version, it is
frequently necessary to dump the database, destroy and recreate the
database files and reload the data from the dump. The postgresql
package attempts to automate this by saving the binaries of the old
package that is being removed so that it can use them to read the
data during the postinst of the new package.
The bug is happening when the postmaster binary from the old package
is being run.
Please cc the bug database in all replies (which will ensure that I see
them).
-----Forwarded Message-----
From: Jeffrey W. Baker <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Bug#138311: Version 7.1 postmaster crashes, impossible to upgrade to
7.2
Date: 14 Mar 2002 09:02:38 -0800
Package: postgresql
Version: 7.2-5
After upgrading postgresql to version 7.2-5 on my ppc machine running
unstable, I am unable to dump and reload my 7.1-format databases. When
I attempt to run the dumpall script, the 7.1 postmaster exits
immediately with status 512 (abort). This makes it impossible to
upgrade the database format to 7.2 and therefore impossible to start the
7.2 postmaster.
One workaround is to delete /var/lib/postgresql/data and reinstall
postgresql.
The machine is an Apple PowerBook, powerpc, running kernel
2.4.18-pre4-ben0, Debian unstable distribution current as of this time.
-jwb
