This bug was fixed in the package postgresql-common - 106ubuntu1
---------------
postgresql-common (106ubuntu1) lucid-proposed; urgency=low
* t/030_errors.t: Check that pg_createcluster leaves the original one
intact if the cluster already exists, also when the original one is not
running. This reproduces LP #661061/Debian #597097.
* pg_createcluster: Be more careful with cleaning up the created cluster if
an error occurs: Do not start the cleanup until we actually passed our
sanity checks and created files for the new cluster. Before, it would
erroneously remove an already existing cluster on a sanity check fail, if
that cluster happened to not be running at the time. (LP: #661061)
Patches cherrypicked from trunk r1024.
* debian/control: Set Vcs-Bzr to lucid branch.
-- Martin Pitt <[email protected]> Mon, 18 Oct 2010 11:04:24 +0200
** Changed in: postgresql-common (Ubuntu Lucid)
Status: Fix Committed => Fix Released
--
pg_createcluster silently deletes existing cluster
https://bugs.launchpad.net/bugs/661061
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
