public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: PostgreSQL Advocacy <[email protected]>
Subject: PostgreSQL 13 press release draft
Date: Mon, 17 Aug 2020 12:06:55 -0400
Message-ID: <[email protected]> (raw)
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
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PostgreSQL 13 press release draft
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox