11.3 is in eoan, marking that task as fix released.
** Changed in: postgresql-11 (Ubuntu Eoan)
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/1828012
Title:
New up
This bug was fixed in the package postgresql-10 - 10.8-0ubuntu0.18.04.1
---
postgresql-10 (10.8-0ubuntu0.18.04.1) bionic-security; urgency=medium
* New upstream release(s) (LP: #1828012)
- Prevent row-level security policies from being bypassed via
selectivity estimators.
This bug was fixed in the package postgresql-10 - 10.8-0ubuntu0.18.10.1
---
postgresql-10 (10.8-0ubuntu0.18.10.1) cosmic-security; urgency=medium
* New upstream release(s) (LP: #1828012)
- Prevent row-level security policies from being bypassed via
selectivity estimators.
This bug was fixed in the package postgresql-11 - 11.3-0ubuntu0.19.04.1
---
postgresql-11 (11.3-0ubuntu0.19.04.1) disco-security; urgency=medium
* New upstream release(s) (LP: #1828012)
- Prevent row-level security policies from being bypassed via
selectivity estimators.
This bug was fixed in the package postgresql-9.5 -
9.5.17-0ubuntu0.16.04.1
---
postgresql-9.5 (9.5.17-0ubuntu0.16.04.1) xenial-security; urgency=medium
* New upstream release(s) (LP: #1828012)
- Prevent row-level security policies from being bypassed via
selectivity estima
Eoan already has
postgresql-11 | 11.3-1 | eoan-proposed
So nothing that would hold us back anymore I guess?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828012
Title:
New upstream microreleases 9
This got released by upstream now, so I'm marking the bug public.
I checked if our pre-generated release links work and they do, so no changelog
changes necessary.
Upstream lists two more CVEs at [1], but those are for other installers
- no need to modify our prepared packages.
We compared the r
