This bug was fixed in the package postgresql-9.1 - 9.1.10-0ubuntu12.04
---------------
postgresql-9.1 (9.1.10-0ubuntu12.04) precise-proposed; urgency=low
* New upstream bug fix release (LP: #1237248). No security issues or
critical issues this time; see HISTORY/changelog.gz for details about bug
fixes.
-- Martin Pitt <[email protected]> Wed, 09 Oct 2013 10:05:58 +0200
** Changed in: postgresql-8.4 (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1237248
Title:
New upstream microreleases 9.1.10, 8.4.18
Status in “postgresql-8.4” package in Ubuntu:
Invalid
Status in “postgresql-9.1” package in Ubuntu:
Fix Released
Status in “postgresql-8.4” source package in Lucid:
Fix Released
Status in “postgresql-8.4” source package in Precise:
Fix Released
Status in “postgresql-9.1” source package in Precise:
Fix Released
Status in “postgresql-9.1” source package in Quantal:
Fix Released
Status in “postgresql-9.1” source package in Raring:
Fix Released
Status in “postgresql-9.1” source package in Saucy:
Fix Released
Bug description:
PostgreSQL will announce new upstream microreleases tomorrow. Just
normal bug fixes this time, no security issues.
I'll update the description with the official annoucement once it goes
public.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1237248/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
