This bug was fixed in the package postgresql-common - 106ubuntu3 --------------- postgresql-common (106ubuntu3) lucid-proposed; urgency=low
* pg_ctlcluster: Drop erroneous $result assignment which was introduced in the previous version due to a mis-merge. postgresql-common (106ubuntu2) lucid-proposed; urgency=low * pg_ctlcluster: Do not remove the PID file after SIGKILLing the postmaster in the "last-ditch effort to shut down" in --force mode. This is a potentially dangerous thing to do when trying to start a second postmaster in parallel while the first one is still being shut down. (see http://archives.postgresql.org/pgsql-general/2012-07/msg00475.php) Patch taken from trunk r1181. (LP: #1042556) -- Martin Pitt <martin.p...@ubuntu.com> Tue, 18 Sep 2012 08:05:03 +0200 ** Changed in: postgresql-common (Ubuntu Lucid) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042556 Title: Critical data loss bug in postgresql-common initscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1042556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs