New bug fix releases: 8.4.8, 8.3.15
Bug #767165 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
|
Undecided
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
postgresql-8.4 (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: postgresql-8.4
PostgreSQL published new microreleases which fix a major potential data-loss bug with using pg_upgrade to 9.0, and some other fixes. No security updates. Please see http://
As per the standing microrelease exception these should go into stables.
To post a comment you must log in.
Note that 8.1 is discontinued upstream, so we won't get a dapper update. Karmic is about to go EOL, so we won't update that either any more.