The PostgreSQL Global Development Group released security updates for all active branches of the PostgreSQL database system, including versions 9.1.4, 9.0.8, 8.4.12 and 8.3.19.
This release contains 42 fixes to version 9.1, and a smaller number of fixes to older versions, including:
- Fix citext upgrade script for collations of citext arrays and domains over citext
- Fixes for timezone handling
- Fix text or char to name casts to perform string truncation correctly in multibyte encodings
- Fix memory copying bug in to_tsquery()
- Ensure txid_current() reports the correct epoch when executed in hot standby
- Fix planner’s handling of sub-SELECTS referencing variables coming from the nullable side of an outer join of the surrounding query
- Fix planning of UNION ALL subqueries with output columns that are not simple variables
- Fix slow session startup when pg_attribute is very large
- Ensure sequential scans check for query cancel reasonably often
- Show whole-row variables safely when printing views or rules
- Fix COPY FROM to properly handle null marker strings that correspond to invalid encoding
- Fix EXPLAIN VERBOSE for writable CTEs containing RETURNING clauses
- Fix PREPARE TRANSACTION to work correctly in the presence of advisory locks
- Fix bugs with temporary or transient tables used in extension scripts
- Ensure autovacuum worker processes perform stack depth checking properly
- Fix logging collector to not lose log coherency under high load
- Fix logging collector to ensure it will restart file rotation after receiving SIGHUP
- Fix WAL replay logic for GIN indexes to not fail if the index was subsequently dropped
- Avoid synchronous replication delay when committing a transaction that only modified temporary tables.
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. Perform post-update steps after the database is restarted.
If you use the citext data type, and you upgraded from a previous major release by running pg_upgrade, please see the release notes for 9.1.4 for important post-upgrade steps.