public inbox for [email protected]help / color / mirror / Atom feed
PostgreSQL 13 press release draft 8+ messages / 4 participants [nested] [flat]
* PostgreSQL 13 press release draft @ 2020-08-17 16:06 Jonathan S. Katz <[email protected]> 0 siblings, 2 replies; 8+ messages in thread From: Jonathan S. Katz @ 2020-08-17 16:06 UTC (permalink / raw) To: PostgreSQL Advocacy <[email protected]> Hi, Attached is a copy of the proposed press release for PostgreSQL 13, with a link to the current document in our git repository as well[1]. Feedback of course is welcome. To provide some context on the overall release: * This follows the previous formats of the press releases to provide feature highlights and be used as a springboard into discovering the features. * The press kit has been slimmed down. This is due to an overall decrease in actual traffic to the press release through the years, though downloads themselves have gone up after the release! This likely due to fragmentation of how people consume PostgreSQL news, as today the release serves more as a "hey the new PostgreSQL software is available!" (And yes, according to the stats, PostgreSQL is more popular than ever ;) This allows us to make the translation effort easier and lower the overall maintenance efforts of the release. * I did some research on the contents of the release itself, and it appears to be comparable to our open source and proprietary database peers. I did look to see if their releases included user testimonials: those tended to be in either separate releases or other media. Given the lack of volunteering for user testimonials over the years and the time it takes to solicit them, I've dropped those efforts, but if someone wants to either contribute or provide some and they are appropriate for the release, I'd be happy to include it. Anyway, I am personally very excited for the PostgreSQL 13 release :) If you have any feedback, please provide it **no later than August 30, 2020 AoE**[2] as after that we will need to begin the translation effort. Thanks! Jonathan [1] https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=releases/13/en/release.en.md [2] https://en.wikipedia.org/wiki/Anywhere_on_Earth 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. <Quote from Core Team member> [PostgreSQL](https://www.postgresql.org), an innovative data management system known for its reliability and robustness, benefits from over 20 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. ### Continued Performance Gains Building on work from the previous PostgreSQL release, PostgreSQL 13 can efficiently handle [duplicate data in B-tree indexes](https://www.postgresql.org/docs/13/btree-implementation.html#BTREE-DEDUPLICATION), the standard database index. This lowers the overall space usage that B-tree indexes require while improving overall query performance. PostgreSQL 13 introduces incremental sorting, where sorted data from an earlier step in a query can accelerate sorting at a later step. Additionally, PostgreSQL can now use the [extended statistics](https://www.postgresql.org/docs/13/planner-stats.html#PLANNER-STATS-EXTENDED) system (accessed via [`CREATE STATISTICS`](https://www.postgresql.org/docs/13/sql-createstatistics.html)) to create improved plans for queries with `OR` clauses and `IN`/`ANY` lookups over lists. In PostgreSQL 13, more types of [aggregate](https://www.postgresql.org/docs/13/functions-aggregate.html) and [grouping set](https://www.postgresql.org/docs/13/queries-table-expressions.html#QUERIES-GROUPING-SETS) queries can leverage PostgreSQL’s efficient hash aggregation functionality, as queries with large aggregates do not have to fit entirely into memory. Queries with [partitioned tables](https://www.postgresql.org/docs/13/ddl-partitioning.html) have received a performance boost, as there are now more cases where partitions can be pruned and where partitions can be directly joined. ### Administration Optimizations [Vacuuming](https://www.postgresql.org/docs/13/routine-vacuuming.html) is an essential part of PostgreSQL administration, enabling the database to reclaim storage space after rows are updated and deleted. This process can also present administrative challenges, though prior PostgreSQL releases have done work to ease the overhead of vacuuming. 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. 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) command can be checked using the new [`pg_verifybackup`](https://www.postgresql.org/docs/13/app-pgverifybackup.html) command. ### Application Development Conveniences PostgreSQL 13 makes it even easier to work with PostgreSQL data types coming from different data sources. This release adds the [`datetime()`](https://www.postgresql.org/docs/13/functions-json.html#FUNCTIONS-SQLJSON-OP-TABLE) function to its SQL/JSON path support, which converts valid time formats (e.g. 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. ### Security Enhancements PostgreSQL’s extension system is a key component of its robustness as it allows developers to expand its functionality. In previous releases, new extensions 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." 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) when using [SCRAM authentication](https://www.postgresql.org/docs/13/sasl-authentication.html#SASL-SCRAM-SHA-256), and the PostgreSQL foreign data wrapper ([`postgres_fdw`](https://www.postgresql.org/docs/13/postgres-fdw.html)) can now use certificate-based authentication. ### About PostgreSQL [PostgreSQL](https://www.postgresql.org) is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. Built on over 30 years of engineering, starting at the University of California, Berkeley, PostgreSQL has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability. ### Press Release Translations * TBD ### Links * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/13/release-13.html) * [Press Kit](https://www.postgresql.org/about/press/) * [Security Page](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [Follow @postgresql on Twitter](https://twitter.com/postgresql) Attachments: [text/plain] release.en.md (6.4K, ../../[email protected]/2-release.en.md) download | inline: 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. <Quote from Core Team member> [PostgreSQL](https://www.postgresql.org), an innovative data management system known for its reliability and robustness, benefits from over 20 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. ### Continued Performance Gains Building on work from the previous PostgreSQL release, PostgreSQL 13 can efficiently handle [duplicate data in B-tree indexes](https://www.postgresql.org/docs/13/btree-implementation.html#BTREE-DEDUPLICATION), the standard database index. This lowers the overall space usage that B-tree indexes require while improving overall query performance. PostgreSQL 13 introduces incremental sorting, where sorted data from an earlier step in a query can accelerate sorting at a later step. Additionally, PostgreSQL can now use the [extended statistics](https://www.postgresql.org/docs/13/planner-stats.html#PLANNER-STATS-EXTENDED) system (accessed via [`CREATE STATISTICS`](https://www.postgresql.org/docs/13/sql-createstatistics.html)) to create improved plans for queries with `OR` clauses and `IN`/`ANY` lookups over lists. In PostgreSQL 13, more types of [aggregate](https://www.postgresql.org/docs/13/functions-aggregate.html) and [grouping set](https://www.postgresql.org/docs/13/queries-table-expressions.html#QUERIES-GROUPING-SETS) queries can leverage PostgreSQL’s efficient hash aggregation functionality, as queries with large aggregates do not have to fit entirely into memory. Queries with [partitioned tables](https://www.postgresql.org/docs/13/ddl-partitioning.html) have received a performance boost, as there are now more cases where partitions can be pruned and where partitions can be directly joined. ### Administration Optimizations [Vacuuming](https://www.postgresql.org/docs/13/routine-vacuuming.html) is an essential part of PostgreSQL administration, enabling the database to reclaim storage space after rows are updated and deleted. This process can also present administrative challenges, though prior PostgreSQL releases have done work to ease the overhead of vacuuming. 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. 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) command can be checked using the new [`pg_verifybackup`](https://www.postgresql.org/docs/13/app-pgverifybackup.html) command. ### Application Development Conveniences PostgreSQL 13 makes it even easier to work with PostgreSQL data types coming from different data sources. This release adds the [`datetime()`](https://www.postgresql.org/docs/13/functions-json.html#FUNCTIONS-SQLJSON-OP-TABLE) function to its SQL/JSON path support, which converts valid time formats (e.g. 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. ### Security Enhancements PostgreSQL’s extension system is a key component of its robustness as it allows developers to expand its functionality. In previous releases, new extensions 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." 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) when using [SCRAM authentication](https://www.postgresql.org/docs/13/sasl-authentication.html#SASL-SCRAM-SHA-256), and the PostgreSQL foreign data wrapper ([`postgres_fdw`](https://www.postgresql.org/docs/13/postgres-fdw.html)) can now use certificate-based authentication. ### About PostgreSQL [PostgreSQL](https://www.postgresql.org) is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. Built on over 30 years of engineering, starting at the University of California, Berkeley, PostgreSQL has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability. ### Press Release Translations * TBD ### Links * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/13/release-13.html) * [Press Kit](https://www.postgresql.org/about/press/) * [Security Page](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [Follow @postgresql on Twitter](https://twitter.com/postgresql) [application/pgp-signature] signature.asc (833B, ../../[email protected]/3-signature.asc) download ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-17 19:30 Simon Riggs <[email protected]> parent: Jonathan S. Katz <[email protected]> 1 sibling, 2 replies; 8+ messages in thread From: Simon Riggs @ 2020-08-17 19:30 UTC (permalink / raw) To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <[email protected]> wrote: > Anyway, I am personally very excited for the PostgreSQL 13 release :) Yes, looks good. Some thematic changes would be useful for this release text: 1. Parallel vacuuming is mentioned first and its probably not the biggest thing we have here. 2. Many of the changes relate directly to large database support * Partitioning changes * Hash Agg * Stats improvements * Btree dedupe won't be noticed by people with smaller databases, but those with larger databases will find those changes dramatic, taken together. As a result, I recommend that we highlight this group of changes and describe the use case they improve, so they can be appreciated better in context. -- Simon Riggs http://www.2ndQuadrant.com/ Mission Critical Databases ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-17 19:31 Simon Riggs <[email protected]> parent: Jonathan S. Katz <[email protected]> 1 sibling, 1 reply; 8+ messages in thread From: Simon Riggs @ 2020-08-17 19:31 UTC (permalink / raw) To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <[email protected]> wrote: > * The press kit has been slimmed down. This is due to an overall > decrease in actual traffic to the press release through the years, > though downloads themselves have gone up after the release! This likely > due to fragmentation of how people consume PostgreSQL news, as today the > release serves more as a "hey the new PostgreSQL software is available!" It's also because this information is no longer available after release, we just show them directly to the more detailed release notes. That's a shame because there is lots of good work in the release announcement. -- Simon Riggs http://www.2ndQuadrant.com/ Mission Critical Databases ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-25 10:08 Peter Eisentraut <[email protected]> parent: Simon Riggs <[email protected]> 1 sibling, 1 reply; 8+ messages in thread From: Peter Eisentraut @ 2020-08-25 10:08 UTC (permalink / raw) To: Simon Riggs <[email protected]>; Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> On 2020-08-17 21:30, Simon Riggs wrote: > Some thematic changes would be useful for this release text: Also, the major features in the release notes should be filled in, ideally in a way that is consistent with the press release. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-29 15:17 Jonathan S. Katz <[email protected]> parent: Simon Riggs <[email protected]> 1 sibling, 0 replies; 8+ messages in thread From: Jonathan S. Katz @ 2020-08-29 15:17 UTC (permalink / raw) To: Simon Riggs <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> Hi Simon, On 8/17/20 3:30 PM, Simon Riggs wrote: > On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <[email protected]> wrote: > >> Anyway, I am personally very excited for the PostgreSQL 13 release :) > > Yes, looks good. > > Some thematic changes would be useful for this release text: > > 1. Parallel vacuuming is mentioned first and its probably not the > biggest thing we have here. > > 2. Many of the changes relate directly to large database support > * Partitioning changes > * Hash Agg > * Stats improvements > * Btree dedupe > won't be noticed by people with smaller databases, but those with > larger databases will find those changes dramatic, taken together. As > a result, I recommend that we highlight this group of changes and > describe the use case they improve, so they can be appreciated better > in context. Thanks for your feedback. Overall, I do agree with your analysis. My original intention was to provide an anchor for some features that people could read into, but going with the "how much of the release will be read / copied" axiom, I rearranged some of the content and took your suggestions. Please see the updated copy attached. This also included feedback from the RMT and expands on some of the copy in the body of the text. Everyone: I'm looking to freeze the copy of the release early this upcoming week so we can begin the translating effort. That said, I will extend to review *deadline to September 2, 2020 AoE* to ensure there is ample time to provide feedback. After that, barring typos / critical errors discovered after that date, the press release content will be frozen. Thanks! Jonathan 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/). PostgreSQL 13 includes significant improvements to its indexing and lookup 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. <Quote from Core Team member> [PostgreSQL](https://www.postgresql.org), an innovative data management system 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. ### Continued Performance Gains Building on work from the previous PostgreSQL release, PostgreSQL 13 can efficiently handle [duplicate data in B-tree indexes](https://www.postgresql.org/docs/13/btree-implementation.html#BTREE-DEDUPLICATION), the standard database index. This lowers the overall space usage that B-tree indexes require while improving overall query performance. PostgreSQL 13 introduces incremental sorting, where sorted data from an earlier step in a query can accelerate sorting at a later step. Additionally, PostgreSQL can now use the [extended statistics](https://www.postgresql.org/docs/13/planner-stats.html#PLANNER-STATS-EXTENDED) system (accessed via [`CREATE STATISTICS`](https://www.postgresql.org/docs/13/sql-createstatistics.html)) to create improved plans for queries with `OR` clauses and `IN`/`ANY` lookups over lists. In PostgreSQL 13, more types of [aggregate](https://www.postgresql.org/docs/13/functions-aggregate.html) and [grouping set](https://www.postgresql.org/docs/13/queries-table-expressions.html#QUERIES-GROUPING-SETS) queries can leverage PostgreSQL’s efficient hash aggregation functionality, as queries with large aggregates do not have to fit entirely into memory. Queries with [partitioned tables](https://www.postgresql.org/docs/13/ddl-partitioning.html) have received a performance boost, as there are now more cases where partitions can be pruned and where partitions can be directly joined. ### Administration Optimizations [Vacuuming](https://www.postgresql.org/docs/13/routine-vacuuming.html) is an essential part of PostgreSQL administration, enabling the database to reclaim storage space after rows are updated and deleted. This process can also present administrative challenges, though prior PostgreSQL releases have done work to ease the overhead of vacuuming. 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. 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 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. ### Application Development Conveniences PostgreSQL 13 makes it even easier to work with PostgreSQL data types coming from different data sources. This release adds the [`datetime()`](https://www.postgresql.org/docs/13/functions-json.html#FUNCTIONS-SQLJSON-OP-TABLE) function to its SQL/JSON path support, which converts valid time formats (e.g. 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 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 PostgreSQL’s extension system is a key component of its robustness as it allows developers to expand its functionality. In previous releases, new extensions 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." 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) when using [SCRAM authentication](https://www.postgresql.org/docs/13/sasl-authentication.html#SASL-SCRAM-SHA-256), and the PostgreSQL foreign data wrapper ([`postgres_fdw`](https://www.postgresql.org/docs/13/postgres-fdw.html)) can now use certificate-based authentication. ### About PostgreSQL [PostgreSQL](https://www.postgresql.org) is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. Built on over 30 years of engineering, starting at the University of California, Berkeley, PostgreSQL has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability. ### Press Release Translations * TBD ### Links * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/13/release-13.html) * [Press Kit](https://www.postgresql.org/about/press/) * [Security Page](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [Follow @postgresql on Twitter](https://twitter.com/postgresql) Attachments: [text/plain] release.en.md (7.6K, ../../[email protected]/2-release.en.md) download | inline: 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/). PostgreSQL 13 includes significant improvements to its indexing and lookup 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. <Quote from Core Team member> [PostgreSQL](https://www.postgresql.org), an innovative data management system 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. ### Continued Performance Gains Building on work from the previous PostgreSQL release, PostgreSQL 13 can efficiently handle [duplicate data in B-tree indexes](https://www.postgresql.org/docs/13/btree-implementation.html#BTREE-DEDUPLICATION), the standard database index. This lowers the overall space usage that B-tree indexes require while improving overall query performance. PostgreSQL 13 introduces incremental sorting, where sorted data from an earlier step in a query can accelerate sorting at a later step. Additionally, PostgreSQL can now use the [extended statistics](https://www.postgresql.org/docs/13/planner-stats.html#PLANNER-STATS-EXTENDED) system (accessed via [`CREATE STATISTICS`](https://www.postgresql.org/docs/13/sql-createstatistics.html)) to create improved plans for queries with `OR` clauses and `IN`/`ANY` lookups over lists. In PostgreSQL 13, more types of [aggregate](https://www.postgresql.org/docs/13/functions-aggregate.html) and [grouping set](https://www.postgresql.org/docs/13/queries-table-expressions.html#QUERIES-GROUPING-SETS) queries can leverage PostgreSQL’s efficient hash aggregation functionality, as queries with large aggregates do not have to fit entirely into memory. Queries with [partitioned tables](https://www.postgresql.org/docs/13/ddl-partitioning.html) have received a performance boost, as there are now more cases where partitions can be pruned and where partitions can be directly joined. ### Administration Optimizations [Vacuuming](https://www.postgresql.org/docs/13/routine-vacuuming.html) is an essential part of PostgreSQL administration, enabling the database to reclaim storage space after rows are updated and deleted. This process can also present administrative challenges, though prior PostgreSQL releases have done work to ease the overhead of vacuuming. 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. 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 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. ### Application Development Conveniences PostgreSQL 13 makes it even easier to work with PostgreSQL data types coming from different data sources. This release adds the [`datetime()`](https://www.postgresql.org/docs/13/functions-json.html#FUNCTIONS-SQLJSON-OP-TABLE) function to its SQL/JSON path support, which converts valid time formats (e.g. 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 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 PostgreSQL’s extension system is a key component of its robustness as it allows developers to expand its functionality. In previous releases, new extensions 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." 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) when using [SCRAM authentication](https://www.postgresql.org/docs/13/sasl-authentication.html#SASL-SCRAM-SHA-256), and the PostgreSQL foreign data wrapper ([`postgres_fdw`](https://www.postgresql.org/docs/13/postgres-fdw.html)) can now use certificate-based authentication. ### About PostgreSQL [PostgreSQL](https://www.postgresql.org) is the world's most advanced open source database, with a global community of thousands of users, contributors, companies and organizations. Built on over 30 years of engineering, starting at the University of California, Berkeley, PostgreSQL has continued with an unmatched pace of development. PostgreSQL's mature feature set not only matches top proprietary database systems, but exceeds them in advanced database features, extensibility, security, and stability. ### Press Release Translations * TBD ### Links * [Download](https://www.postgresql.org/download/) * [Release Notes](https://www.postgresql.org/docs/13/release-13.html) * [Press Kit](https://www.postgresql.org/about/press/) * [Security Page](https://www.postgresql.org/support/security/) * [Versioning Policy](https://www.postgresql.org/support/versioning/) * [Follow @postgresql on Twitter](https://twitter.com/postgresql) [application/pgp-signature] signature.asc (833B, ../../[email protected]/3-signature.asc) download ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-29 15:20 Jonathan S. Katz <[email protected]> parent: Simon Riggs <[email protected]> 0 siblings, 1 reply; 8+ messages in thread From: Jonathan S. Katz @ 2020-08-29 15:20 UTC (permalink / raw) To: Simon Riggs <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> On 8/17/20 3:31 PM, Simon Riggs wrote: > On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <[email protected]> wrote: > >> * The press kit has been slimmed down. This is due to an overall >> decrease in actual traffic to the press release through the years, >> though downloads themselves have gone up after the release! This likely >> due to fragmentation of how people consume PostgreSQL news, as today the >> release serves more as a "hey the new PostgreSQL software is available!" > > It's also because this information is no longer available after > release, we just show them directly to the more detailed release > notes. Well, the numbers are much lower even when it is "news" -- that's the period I typically measure. > > That's a shame because there is lots of good work in the release announcement. Before I helped to write these, I used to refer to them a lot to actually understand what was in a release :) To your point, perhaps we can make it a bit more visible / accessible on the website. The presskits themselves are a bit buried after the release[1] but perhaps we can rearrange some things to make them more visible for longer. It still does not resolve the first problem I mention (traffic to press release down even as news...though will still take the "downloads up" overall problem. So long as we spread awareness!) Jonathan [1] https://www.postgresql.org/about/press/ Attachments: [application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-29 15:21 Jonathan S. Katz <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 0 replies; 8+ messages in thread From: Jonathan S. Katz @ 2020-08-29 15:21 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; Simon Riggs <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]> On 8/25/20 6:08 AM, Peter Eisentraut wrote: > On 2020-08-17 21:30, Simon Riggs wrote: >> Some thematic changes would be useful for this release text: > > Also, the major features in the release notes should be filled in, > ideally in a way that is consistent with the press release. I'll submit a patch proposal on the release notes thread in that respect soon. Jonathan Attachments: [application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: PostgreSQL 13 press release draft @ 2020-08-29 16:13 Magnus Hagander <[email protected]> parent: Jonathan S. Katz <[email protected]> 0 siblings, 0 replies; 8+ messages in thread From: Magnus Hagander @ 2020-08-29 16:13 UTC (permalink / raw) To: Jonathan S. Katz <[email protected]>; +Cc: Simon Riggs <[email protected]>; PostgreSQL Advocacy <[email protected]> On Sat, Aug 29, 2020 at 5:21 PM Jonathan S. Katz <[email protected]> wrote: > On 8/17/20 3:31 PM, Simon Riggs wrote: > > On Mon, 17 Aug 2020 at 17:07, Jonathan S. Katz <[email protected]> > wrote: > > > >> * The press kit has been slimmed down. This is due to an overall > >> decrease in actual traffic to the press release through the years, > >> though downloads themselves have gone up after the release! This likely > >> due to fragmentation of how people consume PostgreSQL news, as today the > >> release serves more as a "hey the new PostgreSQL software is available!" > > > > It's also because this information is no longer available after > > release, we just show them directly to the more detailed release > > notes. > > Well, the numbers are much lower even when it is "news" -- that's the > period I typically measure. > > > > > That's a shame because there is lots of good work in the release > announcement. > > Before I helped to write these, I used to refer to them a lot to > actually understand what was in a release :) > > To your point, perhaps we can make it a bit more visible / accessible on > the website. The presskits themselves are a bit buried after the > release[1] but perhaps we can rearrange some things to make them more > visible for longer. It still does not resolve the first problem I > mention (traffic to press release down even as news...though will still > take the "downloads up" overall problem. So long as we spread awareness!) > Maybe we should link them from the documentation pages, the same way we do with direct links to the release notes? -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/; Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/; ^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2020-08-29 16:13 UTC | newest] Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-08-17 16:06 PostgreSQL 13 press release draft Jonathan S. Katz <[email protected]> 2020-08-17 19:30 ` Simon Riggs <[email protected]> 2020-08-25 10:08 ` Peter Eisentraut <[email protected]> 2020-08-29 15:21 ` Jonathan S. Katz <[email protected]> 2020-08-29 15:17 ` Jonathan S. Katz <[email protected]> 2020-08-17 19:31 ` Simon Riggs <[email protected]> 2020-08-29 15:20 ` Jonathan S. Katz <[email protected]> 2020-08-29 16:13 ` Magnus Hagander <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox