E.38. Release 9.4.11
Prev | Up | Appendix E. Release Notes | Home | Next

## E.38. Release 9.4.11

Release date: 2017-02-09

This release contains a variety of fixes from 9.4.10. For information about new features in the 9.4 major release, see Section E.49.

### E.38.1. Migration to Version 9.4.11

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

However, if your installation has been affected by the bug described in the first changelog entry below, then after updating you may need to take action to repair corrupted indexes.

Also, if you are upgrading from a version earlier than 9.4.10, see Section E.39.

### E.38.2. Changes

- Fix a race condition that could cause indexes built with `CREATE INDEX CONCURRENTLY` to be corrupt (Pavan Deolasee, Tom Lane)

  If `CREATE INDEX CONCURRENTLY` was used to build an index that depends on a column not previously indexed, then rows updated by transactions that ran concurrently with the `CREATE INDEX` command could have received incorrect index entries. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update.

- Ensure that the special snapshot used for catalog scans is not invalidated by premature data pruning (Tom Lane)

  Backends failed to account for this snapshot when advertising their oldest xmin, potentially allowing concurrent vacuuming operations to remove data that was still needed. This led to transient failures along the lines of “cache lookup failed for relation 1255”.

- Unconditionally WAL-log creation of the “init fork” for an unlogged table (Michael Paquier)

  Previously, this was skipped when wal_level = `minimal`, but actually it's necessary even in that case to ensure that the unlogged table is properly reset to empty after a crash.

- Reduce interlocking on standby servers during the replay of btree index vacuuming operations (Simon Riggs)

  This change avoids substantial replication delays that sometimes occurred while replaying such operations.

- If the stats collector dies during hot standby, restart it (Takayuki Tsunakawa)

- Ensure that hot standby feedback works correctly when it's enabled at standby server start (Ants Aasma, Craig Ringer)

- Check for interrupts while hot standby is waiting for a conflicting query (Simon Riggs)

- Avoid constantly respawning the autovacuum launcher in a corner case (Amit Khandekar)

  This fix avoids problems when autovacuum is nominally off and there are some tables that require freezing, but all such tables are already being processed by autovacuum workers.

- Fix check for when an extension member object can be dropped (Tom Lane)

  Extension upgrade scripts should be able to drop member objects, but this was disallowed for serial-column sequences, and possibly other cases.

- Make sure `ALTER TABLE` preserves index tablespace assignments when rebuilding indexes (Tom Lane, Michael Paquier)

  Previously, non-default settings of default_tablespace could result in broken indexes.

- Fix incorrect updating of trigger function properties when changing a foreign-key constraint's deferrability properties with `ALTER TABLE ... ALTER CONSTRAINT` (Tom Lane)

  This led to odd failures during subsequent exercise of the foreign key, as the triggers were fired at the wrong times.

- Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation (Tom Lane)

  This avoids “could not find trigger `NNN`” or “relation `NNN` has no triggers” errors.

- Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via `ALTER TABLE ... INHERIT` (Amit Langote)

  The OID column should be treated the same as regular user columns in this case, but it wasn't, leading to odd behavior in later inheritance changes.

- Fix `CREATE OR REPLACE VIEW` to update the view query before attempting to apply the new view options (Dean Rasheed)

  Previously the command would fail if the new options were inconsistent with the old view definition.

- Report correct object identity during `ALTER TEXT SEARCH CONFIGURATION` (Artur Zakirov)

  The wrong catalog OID was reported to extensions such as logical decoding.

- Check for serializability conflicts before reporting constraint-violation failures (Thomas Munro)

  When using serializable transaction isolation, it is desirable that any error due to concurrent transactions should manifest as a serialization failure, thereby cueing the application that a retry might succeed. Unfortunately, this does not reliably happen for duplicate-key failures caused by concurrent insertions. This change ensures that such an error will be reported as a serialization error if the application explicitly checked for the presence of a conflicting key (and did not find it) earlier in the transaction.

- Prevent multicolumn expansion of `foo``.*` in an `UPDATE` source expression (Tom Lane)

  This led to “UPDATE target count mismatch --- internal error”. Now the syntax is understood as a whole-row variable, as it would be in other contexts.

- Ensure that column typmods are determined accurately for multi-row `VALUES` constructs (Tom Lane)

  This fixes problems occurring when the first value in a column has a determinable typmod (e.g., length for a `varchar` value) but later values don't share the same limit.

- Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string (Tom Lane)

  Normally, a Unicode surrogate leading character must be followed by a Unicode surrogate trailing character, but the check for this was missed if the leading character was the last character in a Unicode string literal (`U&'...'`) or Unicode identifier (`U&"..."`).

- Ensure that a purely negative text search query, such as `!foo`, matches empty `tsvector`s (Tom Dunstan)

  Such matches were found by GIN index searches, but not by sequential scans or GiST index searches.

- Prevent crash when `ts_rewrite()` replaces a non-top-level subtree with an empty query (Artur Zakirov)

- Fix performance problems in `ts_rewrite()` (Tom Lane)

- Fix `ts_rewrite()`'s handling of nested NOT operators (Tom Lane)

- Fix `array_fill()` to handle empty arrays properly (Tom Lane)

- Fix one-byte buffer overrun in `quote_literal_cstr()` (Heikki Linnakangas)

  The overrun occurred only if the input consisted entirely of single quotes and/or backslashes.

- Prevent multiple calls of `pg_start_backup()` and `pg_stop_backup()` from running concurrently (Michael Paquier)

  This avoids an assertion failure, and possibly worse things, if someone tries to run these functions in parallel.

- Avoid discarding `interval`-to-`interval` casts that aren't really no-ops (Tom Lane)

  In some cases, a cast that should result in zeroing out low-order `interval` fields was mistakenly deemed to be a no-op and discarded. An example is that casting from `INTERVAL MONTH` to `INTERVAL YEAR` failed to clear the months field.

- Ensure that cached plans are invalidated by changes in foreign-table options (Amit Langote, Etsuro Fujita, Ashutosh Bapat)

- Fix pg_dump to dump user-defined casts and transforms that use built-in functions (Stephen Frost)

- Fix pg_restore with `--create --if-exists` to behave more sanely if an archive contains unrecognized `DROP` commands (Tom Lane)

  This doesn't fix any live bug, but it may improve the behavior in future if pg_restore is used with an archive generated by a later pg_dump version.

- Fix pg_basebackup's rate limiting in the presence of slow I/O (Antonin Houska)

  If disk I/O was transiently much slower than the specified rate limit, the calculation overflowed, effectively disabling the rate limit for the rest of the run.

- Fix pg_basebackup's handling of symlinked `pg_stat_tmp` and `pg_replslot` subdirectories (Magnus Hagander, Michael Paquier)

- Fix possible pg_basebackup failure on standby server when including WAL files (Amit Kapila, Robert Haas)

- Ensure that the Python exception objects we create for PL/Python are properly reference-counted (Rafa de la Torre, Tom Lane)

  This avoids failures if the objects are used after a Python garbage collection cycle has occurred.

- Fix PL/Tcl to support triggers on tables that have `.tupno` as a column name (Tom Lane)

  This matches the (previously undocumented) behavior of PL/Tcl's `spi_exec` and `spi_execp` commands, namely that a magic `.tupno` column is inserted only if there isn't a real column named that.

- Allow DOS-style line endings in `~/.pgpass` files, even on Unix (Vik Fearing)

  This change simplifies use of the same password file across Unix and Windows machines.

- Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot (Takayuki Tsunakawa)

- Fix psql's tab completion for `ALTER DEFAULT PRIVILEGES` (Gilles Darold, Stephen Frost)

- In psql, treat an empty or all-blank setting of the `PAGER` environment variable as meaning “no pager” (Tom Lane)

  Previously, such a setting caused output intended for the pager to vanish entirely.

- Improve `contrib/dblink`'s reporting of low-level libpq errors, such as out-of-memory (Joe Conway)

- Teach `contrib/dblink` to ignore irrelevant server options when it uses a `contrib/postgres_fdw` foreign server as the source of connection options (Corey Huinker)

  Previously, if the foreign server object had options that were not also libpq connection options, an error occurred.

- On Windows, ensure that environment variable changes are propagated to DLLs built with debug options (Christian Ullrich)

- Sync our copy of the timezone library with IANA release tzcode2016j (Tom Lane)

  This fixes various issues, most notably that timezone data installation failed if the target directory didn't support hard links.

- Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

Prev | Up | Next
E.37. Release 9.4.12 | Home | E.39. Release 9.4.10