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) luc
Sorry, I didn't notice that/when the updated lucid package got accepted
into -proposed. I ran the regression tests again, and they are all
happy.
** Tags removed: verification-done-precise verification-needed
** Tags added: verification-done
--
You received this bug notification because you are
** Changed in: postgresql-common (Debian)
Status: New => 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 m
This bug was fixed in the package postgresql-common - 129ubuntu1
---
postgresql-common (129ubuntu1) precise-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 po
I run the p-common tests and manual tests for precise with the packages
from -proposed, and they all succeed, marking verified for precise.
For lucid I now noticed a slight regression: pg_ctlcluster prints out a
warning
Name "main::result" used only once: possible typo at
/usr/bin/pg_ctlcluste
** Branch linked: lp:ubuntu/lucid-proposed/postgresql-common
** Branch linked: lp:ubuntu/precise-proposed/postgresql-common
--
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 dat
Hello Craig, or anyone else affected,
Accepted into precise-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -pr
Uploaded to lucid-proposed unapproved queue as well. This now needs to
be reviewed by the SRU team.
** Changed in: postgresql-common (Ubuntu Lucid)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Branch linked: lp:~pitti/postgresql/common-lucid
--
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
** Description changed:
Hi
The Debian packages for PostgreSQL (and thus the Ubuntu packages because
of the shared use of pg_wrapper) are subject to a potentially critical
data loss bug because of an unsafe procedure for restarting PostgreSQL.
This issue has been recognised and patc
Uploaded to precise-proposed. I do not know a sensible test case how to
reproduce the failure reliably, but the discussion on the mailing list
makes it rather clear. I'll update the description for SRU as good as I
can.
** Changed in: postgresql-common (Ubuntu Precise)
Status: Triaged => Fi
** Branch linked: lp:~ubuntu-core-dev/postgresql/common-precise
--
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 notific
** Changed in: postgresql-common (Debian)
Status: Unknown => New
--
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
Thanks. I wanted to make sure this didn't slip under the radar in terms
of merging with Debian etc.
--
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-
Adding tasks for LTSes.
** Changed in: postgresql-common (Ubuntu Precise)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: postgresql-common (Ubuntu Precise)
Importance: Undecided => High
** Changed in: postgresql-common (Ubuntu Lucid)
Importance: Undecided => High
--
Yo
This is fixed in Quantal.
** Changed in: postgresql-common (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: postgresql-common (Ubuntu)
Importance: Undecided => High
** Also affects: postgresql-common (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects:
BTW, while the Debian patch says "potentially dangerous", Tom Lane (core
Pg developer & Red Hat package maintainer) says "horridly, horridly
dangerous and stupid".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Debian patch: http://anonscm.debian.org/loggerhead/pkg-postgresql
/postgresql-common/trunk/revision/1181
--
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 postgr
18 matches
Mail list logo
