This bug was fixed in the package postgresql-common - 120+bzr1
---------------
postgresql-common (120+bzr1) oneiric; urgency=low
Upload current Debian bzr head to oneiric.
* debian/supported-versions: Switch Ubuntu 11.10 to 9.1 (LP: #833684) and
also preemtively add Ubuntu 12.04 (which will ship with 9.1, too).
postgresql-common (120) unstable; urgency=low
* PgCommon.pm, cluster_info(): Do not consider external_pid_file
configuration as valid if it is '(none)'. Fixes test suite regression in
version 119.
* debian/supported-versions: Switch to 9.1 as default and testing/unstable
supported version. This will also cause -server-dev-all to only pull in
-9.1.
* PgCommon.pm: Partially revert changes for #606336: postmaster does not
clean up the PID file when it stops, and it is not world readable, so only
its absence is a definitive result. If the PID file is present, do the
port probe to check if it is really running.
-- Martin Pitt <martin.p...@ubuntu.com> Thu, 25 Aug 2011 14:19:59 +0200
** Changed in: postgresql-common (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/833684
Title:
[FFE] Update PostgreSQL to 9.1, drop 9.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/833684/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
