PostgreSQL 9.3.1 Documentation
Prev | Up | Appendix E. Release Notes | Next

# E.3. Release 9.2.5

> Release Date: 2013-10-10

This release contains a variety of fixes from 9.2.4. For information about new features in the 9.2 major release, see Section E.8.

## E.3.1. Migration to Version 9.2.5

A dump/restore is not required for those running 9.2.X.

Also, if you are upgrading from a version earlier than 9.2.2, see the release notes for 9.2.2.

## E.3.2. Changes

- Prevent downcasing of non-ASCII non-double-quoted identifiers in multi-byte encodings (Andrew Dunstan)

  The previous behavior was wrong and confusing.

- Fix memory leak when creating range indexes (Heikki Linnakangas)

- Fix checkpoint memory leak in background writer when `wal_level = hot_standby` (Naoya Anzai)

- Fix memory leak caused by `lo_open()` failure (Heikki Linnakangas)

- Fix memory overcommit bug when `work_mem` is using more than 24GB of memory (Stephen Frost)

- Serializable snapshot fixes (Kevin Grittner, Heikki Linnakangas)

- Fix libpq SSL deadlock bug (Stephen Frost)

- Fix possible SSL network stack corruption in threaded libpq applications (Nick Phillips, Stephen Frost)

- Improve estimate of planner cost when choosing between generic and custom plans (Tom Lane)

  This change will favor generic plans when planning cost is high.

- Properly compute row estimates for boolean columns containing many NULL values (Andrew Gierth)

  Previously tests like `col IS NOT TRUE` and `col IS NOT FALSE` did not properly factor in NULL values when estimating plan costs.

- Fix `UNION ALL` and inheritance queries to properly recheck parameterized paths (Tom Lane)

  This fixes cases where suboptimal query plans could potentially be chosen.

- Prevent pushing down `WHERE` clauses into unsafe `UNION/INTERSECT` subqueries (Tom Lane)

  Previously such push downs could generate errors.

- Fix rare `GROUP BY` query error caused by improperly processed date type modifiers (Tom Lane)

- Fix pg_dump of foreign tables with dropped columns (Andrew Dunstan)

  Previously such cases could cause a pg_upgrade error.

- Reorder pg_dump processing of extension-related rules and event triggers (Joe Conway)

- Force dumping of extension tables if specified by `pg_dump -t` or `-n` (Joe Conway)

- Allow view dump code to better handle dropped columns on base tables (Tom Lane)

- Fix `pg_restore -l` with the directory archive to display the correct format name (Fujii Masao)

- Properly record index comments created using `UNIQUE` and `PRIMARY KEY` syntax (Andres Freund)

  This fixes a parallel pg_restore failure.

- Cause `pg_basebackup -x` with an empty xlog directory to throw an error rather than crashing (Magnus Hagander, Haruka Takatsuka)

- Properly guarantee transmission of WAL files before clean switchover (Fujii Masao)

  Previously, the streaming replication connection might close before all WAL files had been replayed on the standby.

- Improve WAL segment timeline handling during recovery (Heikki Linnakangas)

- Fix `REINDEX TABLE` and `REINDEX DATABASE` to properly revalidate constraints and mark invalidated indexes as valid (Noah Misch)

  `REINDEX INDEX` has always worked properly.

- Avoid deadlocks during insertion into SP-GiST indexes (Teodor Sigaev)

- Fix possible deadlock during concurrent `CREATE INDEX CONCURRENTLY` operations (Tom Lane)

- Fix GiST index lookup crash (Tom Lane)

- Fix `regexp_matches()` handling of zero-length matches (Jeevan Chalke)

  Previously, zero-length matches like '^' could return too many matches.

- Fix crash for overly-complex regular expressions (Heikki Linnakangas)

- Fix regular expression match failures for back references combined with non-greedy quantifiers (Jeevan Chalke)

- Prevent `CREATE FUNCTION` from checking `SET` variables unless function body checking is enabled (Tom Lane)

- Allow `ALTER DEFAULT PRIVILEGES` to operate on schemas without requiring CREATE permission (Tom Lane)

- Loosen restriction on keywords used in queries (Tom Lane)

  Specifically, lessen keyword restrictions for role names, language names, `EXPLAIN` and `COPY` options, and `SET` values. This allows `COPY ... (FORMAT BINARY)` previously `BINARY` required single-quotes.

- Print proper line number during `COPY` failure (Heikki Linnakangas)

- Fix `pgp_pub_decrypt()` so it works for secret keys with passwords (Marko Kreen)

- Have pg_upgrade use `>pg_dump --quote-all-identifiers` to avoid problems with keyword changes between releases (Tom Lane)

- Remove rare inaccurate warning during vacuum of index-less tables (Heikki Linnakangas)

- Improve analyze statistics generation after a cancelled file truncate request (Kevin Grittner)

- Avoid possible failure when performing transaction control commands (e.g `ROLLBACK`) in prepared queries (Tom Lane)

- Allow various spellings of infinity on all platforms (Tom Lane)

  Supported infinity values are "inf", "+inf", "-inf", "infinity", "+infinity", and "-infinity".

- Avoid unnecessary reporting when `track_activities` is off (Tom Lane)

- Expand ability to compare rows to records and arrays (Rafal Rzepecki, Tom Lane)

- Prevent crash when psql's `PSQLRC` variable contains a tilde (Bruce Momjian)

- Add spinlock support for ARM64 (Mark Salter)

- Update time zone data files to tzdata release 2013d for DST law changes in DST law changes in Israel, Morocco, Palestine, Paraguay. Also, historical zone data corrections for Macquarie Island (Tom Lane)

Prev | Home | Next
Release 9.3 | Up | Release 9.2.4