This got fixed a while ago:
postgresql-common (123) unstable; urgency=medium
[...]
* PgCommon.pm, cluster_info(): If we have a PID file and can read it (i. e.
as root), prefer doing this over probing the port. This delivers the
correct result with e. g. "pg_ctlcluster restart" when the port got
changed in the configuration file. (Closes: #643850)
[...]
** Package changed: postgresql-9.1 (Ubuntu) => postgresql-common
(Ubuntu)
** Changed in: postgresql-common (Ubuntu)
Status: New => Triaged
** Bug watch added: Debian Bug tracker #643850
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643850
** Also affects: postgresql-common (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643850
Importance: Unknown
Status: Unknown
** Changed in: postgresql-common (Ubuntu)
Status: Triaged => 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/902808
Title:
Restart doesn't update new port setting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/902808/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
