** Changed in: postgresql-10 (Ubuntu)
Status: Fix Committed => 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/1730661
Title:
New upstream microreleases 9.3.20, 9.5.10 and 9.6.6
T
This bug was fixed in the package postgresql-9.3 - 9.3.20-0ubuntu0.14.04
---
postgresql-9.3 (9.3.20-0ubuntu0.14.04) trusty-security; urgency=medium
* New upstream release (LP: #1730661)
- Details about other changes at full changelog:
https://www.postgresql.org/docs/9.3/st
This bug was fixed in the package postgresql-9.6 - 9.6.6-0ubuntu0.17.04
---
postgresql-9.6 (9.6.6-0ubuntu0.17.04) zesty-security; urgency=medium
* New upstream release (LP: #1730661)
- Previously, a race condition allowed some table rows to be omitted from
the index. It ma
This bug was fixed in the package postgresql-9.6 - 9.6.6-0ubuntu0.17.10
---
postgresql-9.6 (9.6.6-0ubuntu0.17.10) artful-security; urgency=medium
* New upstream release (LP: #1730661)
- Previously, a race condition allowed some table rows to be omitted from
the index. It m
This bug was fixed in the package postgresql-9.5 - 9.5.10-0ubuntu0.16.04
---
postgresql-9.5 (9.5.10-0ubuntu0.16.04) xenial-security; urgency=medium
* New upstream release (LP: #1730661)
- Previously, a race condition allowed some table rows to be omitted from
the index. It
These appear to fix security vulnerabilities. As such, I will release
them as security updates instead of going through the SRU process.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
So far tests hit some known issues lxd-testers and one about pgcluster
setup in some tests needing to avoid blocked ports. Those are all fixed
in later releases already and usually ignored on the SRU (:-/, but a
tradeoff of time).
That said it seems all known good tests are good still - pushing fo
