Hello,
So far 3 out of 3 upgrade failed from woody to sarge, all of them with
the already mentioned message. Last time I debugged through the upgrade
script and I _believe_ I have sent an email to the maintainer about it.
[Sorry that I pour the process into this bug, seems to be the most
related one (upgrade fails miserably). Split/reorder at will.]
1)
Anyway, I think it's about unable to start postmaster for the db reload
because of something I don't remember now (and since this is my very
live db I don't have time to delay upgrade now). I don't think it's
related to 127.0.0.1 bind since I don't bind it there, my db is
accessible to the non-firewalled normal IPs out there [and sockets I
believe, I don't remember changing that], but upgrade shouldn't depend
on that anyway.
2)
Then /usr/lib/postgresql/bin/postgresql-dump choked on encoding file
not available [it is not there, I didn't cared why], which should be
changed from
if [ -n "${create}" ]
then
if [ -n "${verbose}" ]
then
echo "Creating the new database structure" >&2
fi
PGDATA=${POSTGRES_DATA:=/var/lib/postgres/data}
failed=
ENCODING=`cat $ENCODINGFILE 2>/dev/null`
to
ENCODING=`cat $ENCODINGFILE 2>/dev/null` || true
(no time to proper diff sorry). Prevents script to fail immediately.
3)
Then trying
postgresql-dump -t /var/lib/postgres/db.out -e iso-8859-2 -nilv
choked because it populated ...postgres/data/ with the two symlinks
to /etc/postgres/*conf files, these had to be removed first.
So far the db is reloading, I hope there won't be any more surprises.
Peter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
