From 36c69148a27c5c979c9493cb1f879fa5cb5fb8da Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Sat, 29 Aug 2020 11:13:43 -0400 Subject: [PATCH] Second draft of PostgreSQL 13 press release Include feedback from various sources. --- releases/13/en/release.en.md | 46 +++++++++++++++++++++++++----------- 1 file changed, 32 insertions(+), 14 deletions(-) diff --git a/releases/13/en/release.en.md b/releases/13/en/release.en.md index 3387708..bb69864 100644 --- a/releases/13/en/release.en.md +++ b/releases/13/en/release.en.md @@ -2,17 +2,21 @@ The PostgreSQL Global Development Group today announced the release of [PostgreSQL 13](https://www.postgresql.org/docs/13/release-13.html), the latest version of the world’s [most advanced open source database](https://www.postgresql.org/). -With highly requested features like [parallelized vacuuming](https://www.postgresql.org/docs/13/sql-vacuum.html) -and [incremental sorting](https://www.postgresql.org/docs/13/runtime-config-query.html#GUC-ENABLE-INCREMENTAL-SORT), -PostgreSQL 13 provides performance gains, daily administration optimizations, -more conveniences for application developers, and security enhancements. PostgreSQL 13 includes significant improvements to its indexing and lookup -system, including enhancements to queries with aggregates as well as partitions. +system that benefit large databases, including space savings and performance +gains for indexes, faster response times for queries that use aggregates or +partitions, better query planning when using enhanced statistics, and more. + +Along with highly requested features like [parallelized vacuuming](https://www.postgresql.org/docs/13/sql-vacuum.html) +and [incremental sorting](https://www.postgresql.org/docs/13/runtime-config-query.html#GUC-ENABLE-INCREMENTAL-SORT), +PostgreSQL 13 provides a better data management experience for workloads big and +small, with optimizations for daily administration, more conveniences for +application developers, and security enhancements. [PostgreSQL](https://www.postgresql.org), an innovative data management system -known for its reliability and robustness, benefits from over 20 years of open +known for its reliability and robustness, benefits from over 25 years of open source development from a [global developer community](https://www.postgresql.org/community/) and has become the preferred open source relational database for organizations of all sizes. @@ -51,12 +55,19 @@ PostgreSQL 13 continues to improve the vacuuming system with the introduction of [parallelized vacuum for indexes](https://www.postgresql.org/docs/13/sql-vacuum.html). In addition to the vacuuming performance benefits it offers, the use of this new feature can be tuned to specific workloads as administrators can select the -number of parallel workers to run. +number of parallel workers to run. In addition to these performance benefits, +data inserts can now trigger the autovacuum process. + +[Replication slots](https://www.postgresql.org/docs/13/warm-standby.html#STREAMING-REPLICATION-SLOTS), +which are used to prevent write-ahead logs (WAL) from being removed before they +are received by a replica, can be tuned in PostgreSQL 13 to specify the +[max number of WAL files to retain](https://www.postgresql.org/docs/13/runtime-config-replication.html#GUC-MAX-SLOT-WAL-KEEP-SIZE) +and help avoid out-of-disk errors. PostgreSQL 13 also adds more ways an administrator can monitor database -activity, including tracking WAL usage statistics, the progress of streaming -base backups, and the progress of the `ANALYZE` commands. Additionally, the -integrity of the output of the [`pg_basebackup`](https://www.postgresql.org/docs/13/app-pgbasebackup.html) +activity, including referencing WAL usage statistics from `EXPLAIN`, the +progress of streaming base backups, and the progress of the `ANALYZE` commands. +Additionally, the integrity of the output of the [`pg_basebackup`](https://www.postgresql.org/docs/13/app-pgbasebackup.html) command can be checked using the new [`pg_verifybackup`](https://www.postgresql.org/docs/13/app-pgverifybackup.html) command. @@ -69,9 +80,13 @@ ISO 8601 strings) to PostgreSQL-native types. Additionally, the UUID v4 generation function, [`gen_random_uuid()`](https://www.postgresql.org/docs/13/functions-uuid.html), is now available without having to install any extensions. -PostgreSQL’s partitioning system is more flexible, as partitioned tables now -work BEFORE row-level triggers in addition to fully supporting logical -replication. +PostgreSQL’s partitioning system is more flexible, as partitioned tables fully +support logical replication and BEFORE row-level triggers. + +The [`FETCH FIRST`](https://www.postgresql.org/docs/13/sql-select.html#SQL-LIMIT) +syntax in PostgreSQL 13 is now expanded to include the `WITH TIES` clause. When +specified, `WITH TIES` includes any rows that, based on the `ORDER BY` clause, +"tie" with the last row in the result set. ### Security Enhancements @@ -81,7 +96,10 @@ could only be installed by a database superuser. To make it easier to take advantage of PostgreSQL’s extensibility, PostgreSQL 13 adds the concept of a "[trusted extension](https://www.postgresql.org/docs/13/sql-createextension.html)," which allows database users to install extensions that a superuser marks as -"trusted." +"trusted." Certain built-in extensions are marked as trusted by default, +including [`pgcrypto`](https://www.postgresql.org/docs/13/pgcrypto.html), +[`tablefunc`](https://www.postgresql.org/docs/13/tablefunc.html), +[`hstore`](https://www.postgresql.org/docs/13/hstore.html), and more. For applications that require secure authentication methods, PostgreSQL 13 allows for clients to [require channel binding](https://www.postgresql.org/docs/13/libpq-connect.html#LIBPQ-CONNECT-CHANNEL-BINDING) -- 2.39.5