On 11/5/18 9:58 PM, Amit Langote wrote: > On 2018/11/06 11:25, Noah Misch wrote: >> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote: >>> Attached is a draft of the press release for review. Please let me know >>> if there are any corrections/suggestions. >>> * Disallows the creation of a new partition from a trigger that is attached >>> to its parent table to prevent a crash; this behavior could be modified in >>> a future release >>> * Fix that prevents crashes in triggers on tables with recently added >>> columns >> >> I would replace these two with "Fix crashes in triggers". The details are >> too >> esoteric, for the first especially, to list here. > > +1
Thanks for the feedback. I made the suggested changes upthread as well as the above. Please see attached. Funny enough I had a simplified version of the "trigger crashes" in my first draft, but I thought about expanding it given that future behavior could change. I still feel inclined to elaborate on the "Prevent creation of a partition in a trigger attached to its parent table" but perhaps in future release we will just mention that this behavior is again available. Jonathan
2018-11-08 Cumulative Update ============================ The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.1, 10.6, 9.6.11, 9.5.13, 9.4.20, 9.3.25. This release fixes bugs reported over the last three months. All users using the affected versions of PostgreSQL should update during the next convenient upgrade period. Please see the notes on "Updating" below for any post-update steps that may be required if you are using `pg_stat_statements` in your installation. This update is also the final release for PostgreSQL 9.3, which is now end-of-life and will no longer receive any bug or security fixes. If your environment still uses PostgreSQL 9.3, please make plans to update to a community supported version as soon as possible. Please see our [versioning policy](https://www.postgresql.org/support/versioning/) for more information. Bug Fixes and Improvements -------------------------- This update also fixes numerous bugs that were reported in the last several months. Some of these issues affect only version 11, but many affect all supported versions. These releases include fixes that: * Ensure that if a parent partition has an index created in a tablespace, then all child indexes will be created in that same tablespace * Fix several crashes with triggers on partitions * Fix problems with applying `ON COMMIT DELETE ROWS` to a partitioned temporary table * Fix how `NULL` values are handled when using `LEFT JOIN` with a parallelized hash join * Several fixes around using named or defaulted arguments in `CALL` statements * Fix for strict aggregate functions (i.e. aggregates that cannot accept `NULL` inputs) with ORDER BY columns that enforces the strictness check * Fix with `CASE` statements where an expression was cast to an array type * Fix a memory leak that occurred on a specific case of using a SP-GiST index * Fix for `pg_verify_checksums` incorrectly reporting on files that are not expected to have checksums * Prevent the PostgreSQL server from starting when `wal_level` is set to a value that cannot support an existing replication slot * Ensure that the server will process already-received NOTIFY and SIGTERM interrupts before waiting for client input * Fix for character-class checks on Windows for Unicode characters above U+FFFF, which affected full-text search as well as `contrib/ltree` and `contrib/pg_trgm` * Fix a case where `psql` would not report the receipt of a message from a `NOTIFY` call until after the next command * Fix build problems on macOS 10.14 (Mojave) * Several build fixes for the Windows platform This updates also contains tzdata release 2018g for DST law changes in Chile, Fiji, Morocco, and Russia (Volgograd), plus historical corrections for China, Hawaii, Japan, Macau, and North Korea. PostgreSQL 9.3 is End-of-Life (EOL) ----------------------------------- PostgreSQL 9.3 is now end-of-life and will no longer receive any bug or security fixes. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. Please see our [versioning policy](https://www.postgresql.org/support/versioning/) for more information. 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. If your system is using `pg_stat_statements` and you are running a version of PostgreSQL 10 or PostgreSQL 11, we advise that you execute the following command after upgrading: `ALTER EXTENSION pg_stat_statements UPDATE;` 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. Links ----- * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/current/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)
signature.asc
Description: OpenPGP digital signature
