New bug fix releases: 8.4.9, 8.3.16
Bug #866049 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-8.3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Ubuntu Security Team | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
postgresql-8.4 (Debian) |
Fix Released
|
Unknown
|
|||
postgresql-8.4 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Medium
|
Ubuntu Security Team |
Bug Description
PostgreSQL published new microreleases about a week ago: http://
This fixes a security issue and several bugs, as usual. As per the standing microrelease exception these should go into stables.
CVE References
Changed in postgresql-8.4 (Debian): | |
status: | Unknown → Fix Released |
To post a comment you must log in.
All these are already fixed in postgresql-9.1 9.1.1 in Oneiric.