This bug was fixed in the package postgresql-common - 88
---------------
postgresql-common (88) unstable; urgency=low
* t/030_errors.t: Add various test cases for stopping stopped clusters with
stale or corrupt PID files, with and without --force. This reproduces
#473879.
* pg_ctlcluster: On stop, clean up stale/corrupt PID files if the server is
not running. Also fix a taint error and simplify the code a bit.
(Closes: #473879)
* t/030_errors.t: Test graceful handling of absent /var/lib/postgresql.
(Reproduces LP #210322). Adapt 020_create_sql_remove.t accordingly.
* pg_ctlcluster: Check early whether the data directory exists and is
accessible, to avoid lots of Perl warning clutter. (LP: #210322)
* pg_createcluster POD: Clarify what "integrating existing cluster data
directory" means: configuration files must already be present, we cannot
create them out of thin air. (Closes: #475954)
* pg_maintenance: Sort versions for predictable output (looks nicer and
unbreaks the test suite).
-- Ubuntu Archive Auto-Sync <[EMAIL PROTECTED]> Fri, 02 May 2008
02:23:00 +0100
** Changed in: postgresql-common (Ubuntu)
Status: Fix Committed => Fix Released
--
postgres init script fails uncleanly if cluster directory is missing
https://bugs.launchpad.net/bugs/210322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
