PostgreSQL 2013-10-10 Update Release

Posted on 2013-10-10 by PostgreSQL Global Development Group

The PostgreSQL Global Development Group has released a bug-fix update to all current versions of the PostgreSQL database system, including versions 9.3.1, 9.2.5, 9.1.10, 9.0.14, and 8.4.18. This release fixes many minor issues reported by our community over the last six months. All users should update their PostgreSQL installations at the next regular maintenance window.

In this release are fixes for the recently-released version 9.3, including:

  • Update hstore extension with JSON functionality
  • Prevent memory leak when creating range indexes
  • Fix libpq SSL deadlock bug

In addition to the above, there are a few dozen minor bug fixes for older versions. These patches were already included in 9.3.0 when released. Among them are:

  • Guarantee transmission of all WAL files before replica failover
  • Prevent downcasing of non-ASCII identifiers
  • Fix several minor memory leaks
  • Correct overcommit behavior when using more than 24GB of work memory
  • Improve planner cost estimates for choosing generic plans
  • Fix estimates of NULL rows in boolean columns
  • Make UNION ALL and inheritance query plans recheck parameterized paths
  • Correct pg_dump bugs for foreign tables, views, and extensions
  • Prevent a parallel pg_restore failure on certain indexes
  • Make REINDEX revalidate constraints
  • Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
  • Prevent GiST index lookup crash
  • Fix several regular expression failures
  • Allow ALTER DEFAULT PRIVILEGES to work on all schemas
  • Loosen restrictions on keywords
  • Allow various spellings of infinity
  • Expand ability to compare rows to records and arrays
  • Prevent psql client crash on bad PSQLRC file
  • Add spinlock support for ARM64

Note that users of the hstore extension on version 9.3 must take an additional, post upgrade step of running "ALTER EXTENSION hstore UPDATE" in each database after update.

As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Users who have skipped multiple update releases may need to perform additional, post-update steps; see the Release Notes for details.

Links: * Download * Release Notes