2019-05-09 Cumulative Update Release
====================================

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22. This release contains fixes for over 60 bugs reported over the last three months.

Users should plan to apply this update at the next scheduled downtime.

Bug Fixes and Improvements
--------------------------

This update fixes over 60 bugs that were reported in the last several months. Some of these issues affect only version 11, but many affect all supported versions.

Some of these fixes include:

* Several catalog corruption fixes, including one related to running `ALTER TABLE` on a partitioned table
* Several fixes for partitioning
* Avoid server crash when an error occurs while trying to persist a cursor query across a transaction commit
* Avoid O(N^2) performance issue when rolling back a transaction that created many tables
* Fix possible “could not access status of transaction” failures in `txid_status()`
* Fix updatable views to handle explicit DEFAULT items in `INSERT .. VALUES` statements where there are multiple VALUES rows
* Fix CREATE VIEW to allow zero-column views
* Add missing support for the `CREATE TABLE IF NOT EXISTS .. AS EXECUTE ..` statement
* Ensure that sub-SELECTs appearing in row-level-security policy expressions are executed with the correct user's permissions
* Accept XML documents as valid values of type xml when xmloption is set to content, as required by SQL:2006 and later
* Fix incompatibility of GIN-index WAL records that were introduced in 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21 that affected replica servers running these versions reading in changes to GIN indexes from primary servers of older versions
* Several memory leak fixes as well as fixes to management of dynamic shared memory
* Relax panics on fsync failures for certain cases where a failure indicated "operation not supported"
* Several fixes to the query planner, several of which should lead to planning improvements
* Fix incorrect strictness check for array coercion expressions
* Fix race condition in which a hot-standby postmaster could fail to shut down after receiving a smart-shutdown request
* Several fixes for SCRAM authentication
* Fix handling of lc\_time settings that imply an encoding different from the database's encoding
* Create the `current_logfiles` file with the same permissions as other files in the server's `data` directory
* Several ecpg fixes
* Make `pg_dump` recreate table partitions using `ATTACH PARTITION` instead of `CREATE TABLE .. PARTITION OF`
* Make `pg_verify_checksums` verify that the data directory it's pointed at is of the right PostgreSQL version
* Several fixes for `conritb/postgres_fdw`, including one for remote partitions where an UPDATE could lead to incorrect results or a crash
* Several Windows fixes

This update also contains tzdata release 2019a for DST law changes in Palestine and Metlakatla, plus historical corrections for Israel. Etc/UCT is now a backward-compatibility link to Etc/UTC, instead of being a separate zone that generates the abbreviation UCT, which nowadays is typically a typo. PostgreSQL will still accept UCT as an input zone abbreviation, but it won't output it.

Updating
--------

All PostgreSQL update releases are cumulative. 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 shutdown PostgreSQL and update its binaries.

Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.

PostgreSQL 9.4 will stop receiving fixes on February 13, 2020. Please see our [versioning policy](https://www.postgresql.org/support/versioning/) for more information.

Links
-----
* [Download](https://www.postgresql.org/download/)
* [Release Notes](https://www.postgresql.org/docs/11/release.html)
* [Security Page](https://www.postgresql.org/support/security/)
* [Versioning Policy](https://www.postgresql.org/support/versioning/)
* [Follow @postgresql on Twitter](https://twitter.com/postgresql)
