Opened 8 years ago

Closed 8 years ago

#6606 closed enhancement (fixed)


Reported by: Fernando de Oliveira Owned by: Fernando de Oliveira
Priority: normal Milestone: 7.8
Component: BOOK Version: SVN
Severity: normal Keywords:



PostgreSQL 9.4.4, 9.3.9, 9.2.13, 9.1.18 & 9.0.22 Released!
Posted on June 12, 2015
2015-06-12 Update Release

The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 9.4.4, 9.3.9,
9.2.13, 9.1.18 and 9.0.22. This release primarily fixes issues not
successfully fixed in prior releases. It should be applied as soon as
possible all users of major versions 9.3 and 9.4. Other users should
apply at the next available downtime.

Crash Recovery Fixes

Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and
9.4 with "multixact wraparound", but failed to account for issues doing
multixact cleanup during crash recovery. This could cause servers to be
unable to restart after a crash. As such, all users of 9.3 and 9.4
should apply this update as soon as possible.

Servers previously upgraded to PostgreSQL 9.3 using pg_upgrade, even
those servers now running PostgreSQL 9.4 due to another upgrade, may
experience an immediate autovacuum of all tables after applying this
update. For large databases, consider a controlled manual VACUUM, before
updating, to better regulate the performance consequences of this
critical maintenance. Please see the release notes for details.

Other Fixes and Improvements

In addition to the above, a few other minor issues were patched in this
release. These fixes include:

   • Prevent failure to invalidate relation cache init file
   • Avoid deadlock between new sessions and CREATE/DROP DATABASE
   • Improve query planning for semi-joins and anti-joins


Change History (2)

comment:1 by Fernando de Oliveira, 8 years ago

Owner: changed from blfs-book@… to Fernando de Oliveira
Status: newassigned

comment:2 by Fernando de Oliveira, 8 years ago

Resolution: fixed
Status: assignedclosed

Fixed at r16128.

Note: See TracTickets for help on using tickets.