public inbox for [email protected]
help / color / mirror / Atom feedPostgreSQL 16 Beta 1 release announcement draft
9+ messages / 3 participants
[nested] [flat]
* PostgreSQL 16 Beta 1 release announcement draft
@ 2023-05-19 04:18 Jonathan S. Katz <[email protected]>
2023-05-19 14:42 ` Re: PostgreSQL 16 Beta 1 release announcement draft Justin Clift <[email protected]>
2023-05-19 15:02 ` Re: PostgreSQL 16 Beta 1 release announcement draft Justin Clift <[email protected]>
2023-05-20 19:24 ` Re: PostgreSQL 16 Beta 1 release announcement draft Cédric Villemain <[email protected]>
2023-05-21 17:06 ` Re: PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
0 siblings, 4 replies; 9+ messages in thread
From: Jonathan S. Katz @ 2023-05-19 04:18 UTC (permalink / raw)
To: PostgreSQL Advocacy <[email protected]>
Hi,
Attached is a draft of the release announcement for PostgreSQL 16 Beta
1. The goal of this announcement is to get people excited about testing
the beta and highlight many of the new features.
Please review for inaccuracies, omissions, and other suggestions / errors.
Please provide feedback no later than May 24, 0:00 AoE. This will give
me enough time to incorporate the changes prior to the release the next day.
Thanks,
Jonathan
The PostgreSQL Global Development Group announces that the first beta release of
PostgreSQL 16 is now [available for download](https://www.postgresql.org/download/).
This release contains previews of all features that will be available when
PostgreSQL 16 is made generally available, though some details of the release
can change during the beta period.
You can find information about all of the features and changes found in
PostgreSQL 16 in the [release notes](https://www.postgresql.org/docs/16/release-16.html):
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 16 on your systems to help us eliminate
bugs or other issues that may exist. While we do not advise you to run
PostgreSQL 16 Beta 1 in production environments, we encourage you to find ways
to run your typical application workloads against this beta release.
Your testing and feedback will help the community ensure that the PostgreSQL 16
release upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our [beta testing process](https://www.postgresql.org/developer/beta/) and how
you can contribute:
[https://www.postgresql.org/developer/beta/](https://www.postgresql.org/developer/beta/)
PostgreSQL 16 Feature Highlights
--------------------------------
### Logical replication enhancements
Logical replication lets PostgreSQL users stream data in real-time to other
PostgreSQL or other external systems that implement the logical protocol. Until
PostgreSQL 16, users could only create logical replication publishers on primary
instances. PostgreSQL 16 adds the ability to perform logical decoding on a
standby instance, given users more options to distribute their workload, for
example, use a standby that's less busy than a primary to logically replicate
changes.
PostgreSQL 16 also includes several performance improvements to logical
replication. This includes allowing the subscriber to apply large transactions
in parallel, use indexes other than the `PRIMARY KEY` to perform lookups during
`UPDATE` or `DELETE` operations, and allow for tables to be copied using binary
format during initialization.
### Performance
PostgreSQL 16 includes performance improvements in query execution. This release
adds more query parallelism, including allowing `FULL` and `OUTER` joins to
execute in parallel, and parallel execution of the `string_agg` and `array_agg`
aggregate functions. Additionally, PostgreSQL 16 can use incremental sorts in
`SELECT DISTINCT` queries. There are also several optimizations for
[window queries](https://www.postgresql.org/docs/devel/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS),
improvements in lookups for `RANGE` and `LIST` partitions, and support for
"anti-joins" in `RIGHT` and `OUTER` queries.
This release also introduces support for CPU acceleration using SIMD for both
x86 and ARM architectures, including optimizations for processing ASCII and JSON
strings, and array and substransaction searches. Additionally, PostgreSQL 16
introduces [load balancing](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-LOAD-BALANCE-HOSTS)
to libpq, the client library for PostgreSQL.
### Developer Experience
PostgreSQL 16 continues to to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
standard for manipulating [JSON](https://www.postgresql.org/docs/devel/datatype-json.html)
data, including support for SQL/JSON constructors (e.g. `JSON_ARRAY()`,
`JSON_ARRAYAGG()` et al), and identity functions (`IS JSON`). This release also
adds the SQL standard [`ANY_VALUE`](https://www.postgresql.org/docs/devel/functions-aggregate.html#id-1.5.8.27.5.2.4.1.1.1.1)
aggregate function, which returns any arbitrary value from the aggregate set.
For convenience, PostgreSQL 16 now lets you specify non-decimal integer
literals, such as `0xff`, `0o777`, and `0b101010`, and use thousands separators,
such as `5_432`.
This release adds support for the extended query protocol to the [`psql`](https://www.postgresql.org/docs/devel/app-psql.html)
client. Users can execute a query, e.g. `SELECT $1 + $2`, and use the
[`\bind`](https://www.postgresql.org/docs/devel/app-psql.html#APP-PSQL-META-COMMAND-BIND)
command to substitute the variables.
### Security features
PostgreSQL 16 continues to give users to the ability grant privileged access to
features without requiring superuser with new
[predefined roles](https://www.postgresql.org/docs/devel/predefined-roles.html).
These include `pg_maintain`, which enables execution of operations such as
`VACUUM`, `ANALYZE`, `REINDEX`, and others, and `pg_createsubscription`, which
allows users to create a logical replication subscription. Additionally,
starting with release, logical replication subscribers execute transactions on a
table as the table owner, not the superuser.
PostgreSQL 16 now lets you use regular expressions in the [`pg_hba.conf`](https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html)
and [`pg_ident.conf`](https://www.postgresql.org/docs/devel/auth-username-maps.html)
files for matching user and databases names. Additionally, PostgreSQL 16 adds
the ability to include other files in both `pg_hba.conf` and `pg_ident.conf`.
PostgreSQL 16 also adds support for the SQL standard [`SYSTEM_USER`](https://www.postgresql.org/docs/devel/functions-info.html#id-1.5.8.32.3.4.2.2.24.1.1.1)
keyword, which returns the username and authentication method used to establish
a session.
PostgreSQL 16 also adds support for Kerberos credential delegation, which allows
extensions such as `postgres_fdw` and `dblink` to use the authenticated
credentials to connected to other services. This release also adds several new
security-oriented connection parameters for clients. This includes [`require_auth`](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH),
where a client can specify which authentication methods it is willing to accept
from the server. You can now also set `sslrootcert` to `system` to specify that
PostgreSQL can use the trusted certificate authority (CA) store for that
operating system.
### Operations
PostgreSQL 16 adds several new monitoring features, including the new
[`pg_stat_io`](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW)
view that provides information on I/O statistics. This release also provides a
timestamp for the last time that a [table or index was scanned](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW).
There are also improvements to the normalization algorithm used for
`pg_stat_activity`.
This release includes improvements to the page freezing strategy, which helps
the performance of vacuuming and other maintenance operations. PostgreSQL 16
also improves general support for text collations, which provide rules for how
text is sorted. PostgreSQL 16 sets ICU to be the default collation provider, and
also adds support for the predefined `unicode` and `ucs_basic` collations.
PostgreSQL 16 adds additional compression options to `pg_dump`, including
support for both `lz4` and `zstd` compression.
### Other Notable Changes
For Windows installations, PostgreSQL 16 now supports a minimum version of
Windows 10. Additionally, PostgreSQL 16 removes the `promote_trigger_file`
option to enable the promotion of a standby. Users should use the
`pg_ctl promote` command or `pg_promote()` function to promote a standby.
PostgreSQL 16 introduced the Meson build system, which will ultimately replace
Autoconf. This release also adds foundational support for developmental features
that will be improved upon in future releases, including a developer flag to
enable DirectIO and the ability to use logical replication to bidirectionally
replicate between two tables when `origin=none` is specified in the subscriber.
Additional Features
-------------------
Many other new features and improvements have been added to PostgreSQL 16. Many
of these may also be helpful for your use cases. Please see the
[release notes](https://www.postgresql.org/docs/16/release-16.html) for a
complete list of new and changed features:
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
Testing for Bugs & Compatibility
--------------------------------
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools in order to
find bugs and regressions before the general availability of PostgreSQL 16. As
this is a Beta, minor changes to database behaviors, feature details, and APIs
are still possible. Your feedback and testing will help determine the final
tweaks on the new features, so please test in the near future. The quality of
user testing helps determine when we can make a final release.
A list of [open issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
is publicly available in the PostgreSQL wiki. You can
[report bugs](https://www.postgresql.org/account/submitbug/) using this form on
the PostgreSQL website:
[https://www.postgresql.org/account/submitbug/](https://www.postgresql.org/account/submitbug/)
Beta Schedule
-------------
This is the first beta release of version 16. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release in late 2023. For further
information please see the [Beta Testing](https://www.postgresql.org/developer/beta/)
page.
Links
-----
* [Download](https://www.postgresql.org/download/)
* [Beta Testing Information](https://www.postgresql.org/developer/beta/)
* [PostgreSQL 16 Beta Release Notes](https://www.postgresql.org/docs/16/release-16.html)
* [PostgreSQL 16 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
* [Submit a Bug](https://www.postgresql.org/account/submitbug/)
Attachments:
[text/plain] 16beta1.md (9.9K, 2-16beta1.md)
download | inline:
The PostgreSQL Global Development Group announces that the first beta release of
PostgreSQL 16 is now [available for download](https://www.postgresql.org/download/).
This release contains previews of all features that will be available when
PostgreSQL 16 is made generally available, though some details of the release
can change during the beta period.
You can find information about all of the features and changes found in
PostgreSQL 16 in the [release notes](https://www.postgresql.org/docs/16/release-16.html):
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 16 on your systems to help us eliminate
bugs or other issues that may exist. While we do not advise you to run
PostgreSQL 16 Beta 1 in production environments, we encourage you to find ways
to run your typical application workloads against this beta release.
Your testing and feedback will help the community ensure that the PostgreSQL 16
release upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our [beta testing process](https://www.postgresql.org/developer/beta/) and how
you can contribute:
[https://www.postgresql.org/developer/beta/](https://www.postgresql.org/developer/beta/)
PostgreSQL 16 Feature Highlights
--------------------------------
### Logical replication enhancements
Logical replication lets PostgreSQL users stream data in real-time to other
PostgreSQL or other external systems that implement the logical protocol. Until
PostgreSQL 16, users could only create logical replication publishers on primary
instances. PostgreSQL 16 adds the ability to perform logical decoding on a
standby instance, given users more options to distribute their workload, for
example, use a standby that's less busy than a primary to logically replicate
changes.
PostgreSQL 16 also includes several performance improvements to logical
replication. This includes allowing the subscriber to apply large transactions
in parallel, use indexes other than the `PRIMARY KEY` to perform lookups during
`UPDATE` or `DELETE` operations, and allow for tables to be copied using binary
format during initialization.
### Performance
PostgreSQL 16 includes performance improvements in query execution. This release
adds more query parallelism, including allowing `FULL` and `OUTER` joins to
execute in parallel, and parallel execution of the `string_agg` and `array_agg`
aggregate functions. Additionally, PostgreSQL 16 can use incremental sorts in
`SELECT DISTINCT` queries. There are also several optimizations for
[window queries](https://www.postgresql.org/docs/devel/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS),
improvements in lookups for `RANGE` and `LIST` partitions, and support for
"anti-joins" in `RIGHT` and `OUTER` queries.
This release also introduces support for CPU acceleration using SIMD for both
x86 and ARM architectures, including optimizations for processing ASCII and JSON
strings, and array and substransaction searches. Additionally, PostgreSQL 16
introduces [load balancing](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-LOAD-BALANCE-HOSTS)
to libpq, the client library for PostgreSQL.
### Developer Experience
PostgreSQL 16 continues to to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
standard for manipulating [JSON](https://www.postgresql.org/docs/devel/datatype-json.html)
data, including support for SQL/JSON constructors (e.g. `JSON_ARRAY()`,
`JSON_ARRAYAGG()` et al), and identity functions (`IS JSON`). This release also
adds the SQL standard [`ANY_VALUE`](https://www.postgresql.org/docs/devel/functions-aggregate.html#id-1.5.8.27.5.2.4.1.1.1.1)
aggregate function, which returns any arbitrary value from the aggregate set.
For convenience, PostgreSQL 16 now lets you specify non-decimal integer
literals, such as `0xff`, `0o777`, and `0b101010`, and use thousands separators,
such as `5_432`.
This release adds support for the extended query protocol to the [`psql`](https://www.postgresql.org/docs/devel/app-psql.html)
client. Users can execute a query, e.g. `SELECT $1 + $2`, and use the
[`\bind`](https://www.postgresql.org/docs/devel/app-psql.html#APP-PSQL-META-COMMAND-BIND)
command to substitute the variables.
### Security features
PostgreSQL 16 continues to give users to the ability grant privileged access to
features without requiring superuser with new
[predefined roles](https://www.postgresql.org/docs/devel/predefined-roles.html).
These include `pg_maintain`, which enables execution of operations such as
`VACUUM`, `ANALYZE`, `REINDEX`, and others, and `pg_createsubscription`, which
allows users to create a logical replication subscription. Additionally,
starting with release, logical replication subscribers execute transactions on a
table as the table owner, not the superuser.
PostgreSQL 16 now lets you use regular expressions in the [`pg_hba.conf`](https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html)
and [`pg_ident.conf`](https://www.postgresql.org/docs/devel/auth-username-maps.html)
files for matching user and databases names. Additionally, PostgreSQL 16 adds
the ability to include other files in both `pg_hba.conf` and `pg_ident.conf`.
PostgreSQL 16 also adds support for the SQL standard [`SYSTEM_USER`](https://www.postgresql.org/docs/devel/functions-info.html#id-1.5.8.32.3.4.2.2.24.1.1.1)
keyword, which returns the username and authentication method used to establish
a session.
PostgreSQL 16 also adds support for Kerberos credential delegation, which allows
extensions such as `postgres_fdw` and `dblink` to use the authenticated
credentials to connected to other services. This release also adds several new
security-oriented connection parameters for clients. This includes [`require_auth`](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH),
where a client can specify which authentication methods it is willing to accept
from the server. You can now also set `sslrootcert` to `system` to specify that
PostgreSQL can use the trusted certificate authority (CA) store for that
operating system.
### Operations
PostgreSQL 16 adds several new monitoring features, including the new
[`pg_stat_io`](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW)
view that provides information on I/O statistics. This release also provides a
timestamp for the last time that a [table or index was scanned](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW).
There are also improvements to the normalization algorithm used for
`pg_stat_activity`.
This release includes improvements to the page freezing strategy, which helps
the performance of vacuuming and other maintenance operations. PostgreSQL 16
also improves general support for text collations, which provide rules for how
text is sorted. PostgreSQL 16 sets ICU to be the default collation provider, and
also adds support for the predefined `unicode` and `ucs_basic` collations.
PostgreSQL 16 adds additional compression options to `pg_dump`, including
support for both `lz4` and `zstd` compression.
### Other Notable Changes
For Windows installations, PostgreSQL 16 now supports a minimum version of
Windows 10. Additionally, PostgreSQL 16 removes the `promote_trigger_file`
option to enable the promotion of a standby. Users should use the
`pg_ctl promote` command or `pg_promote()` function to promote a standby.
PostgreSQL 16 introduced the Meson build system, which will ultimately replace
Autoconf. This release also adds foundational support for developmental features
that will be improved upon in future releases, including a developer flag to
enable DirectIO and the ability to use logical replication to bidirectionally
replicate between two tables when `origin=none` is specified in the subscriber.
Additional Features
-------------------
Many other new features and improvements have been added to PostgreSQL 16. Many
of these may also be helpful for your use cases. Please see the
[release notes](https://www.postgresql.org/docs/16/release-16.html) for a
complete list of new and changed features:
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
Testing for Bugs & Compatibility
--------------------------------
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools in order to
find bugs and regressions before the general availability of PostgreSQL 16. As
this is a Beta, minor changes to database behaviors, feature details, and APIs
are still possible. Your feedback and testing will help determine the final
tweaks on the new features, so please test in the near future. The quality of
user testing helps determine when we can make a final release.
A list of [open issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
is publicly available in the PostgreSQL wiki. You can
[report bugs](https://www.postgresql.org/account/submitbug/) using this form on
the PostgreSQL website:
[https://www.postgresql.org/account/submitbug/](https://www.postgresql.org/account/submitbug/)
Beta Schedule
-------------
This is the first beta release of version 16. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release in late 2023. For further
information please see the [Beta Testing](https://www.postgresql.org/developer/beta/)
page.
Links
-----
* [Download](https://www.postgresql.org/download/)
* [Beta Testing Information](https://www.postgresql.org/developer/beta/)
* [PostgreSQL 16 Beta Release Notes](https://www.postgresql.org/docs/16/release-16.html)
* [PostgreSQL 16 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
* [Submit a Bug](https://www.postgresql.org/account/submitbug/)
[application/pgp-signature] OpenPGP_signature (840B, 3-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
@ 2023-05-19 14:42 ` Justin Clift <[email protected]>
2023-05-21 16:56 ` Re: PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
3 siblings, 1 reply; 9+ messages in thread
From: Justin Clift @ 2023-05-19 14:42 UTC (permalink / raw)
To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
2023-05-19 14:18, Jonathan S. Katz wrote:
> Hi,
>
> Attached is a draft of the release announcement for PostgreSQL 16 Beta
> 1. The goal of this announcement is to get people excited about
> testing the beta and highlight many of the new features.
>
> Please review for inaccuracies, omissions, and other suggestions /
> errors.
Would you be ok with capitalising the word "Community" in "PostgreSQL
community" in it?
It's just a subtle emphasis thing, but still... :)
+ Justin
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
2023-05-19 14:42 ` Re: PostgreSQL 16 Beta 1 release announcement draft Justin Clift <[email protected]>
@ 2023-05-21 16:56 ` Jonathan S. Katz <[email protected]>
0 siblings, 0 replies; 9+ messages in thread
From: Jonathan S. Katz @ 2023-05-21 16:56 UTC (permalink / raw)
To: Justin Clift <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
On 5/19/23 10:42 AM, Justin Clift wrote:
> 2023-05-19 14:18, Jonathan S. Katz wrote:
>> Hi,
>>
>> Attached is a draft of the release announcement for PostgreSQL 16 Beta
>> 1. The goal of this announcement is to get people excited about
>> testing the beta and highlight many of the new features.
>>
>> Please review for inaccuracies, omissions, and other suggestions /
>> errors.
>
> Would you be ok with capitalising the word "Community" in "PostgreSQL
> community" in it?
>
> It's just a subtle emphasis thing, but still... :)
We don't do this anywhere else on the website or documentation. All the
other references in the doc just use "community" without "PostgreSQL" so
if anything we could arguably drop "PostgreSQL" all together there or
reword the sentence, but I'm not generally inclined to capitalize
"community" in this context.
Thanks,
Joanthan
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, 2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
@ 2023-05-19 15:02 ` Justin Clift <[email protected]>
2023-05-21 17:02 ` Re: PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
3 siblings, 1 reply; 9+ messages in thread
From: Justin Clift @ 2023-05-19 15:02 UTC (permalink / raw)
To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
On 2023-05-19 14:18, Jonathan S. Katz wrote:
> Hi,
>
> Attached is a draft of the release announcement for PostgreSQL 16 Beta
> 1. The goal of this announcement is to get people excited about
> testing the beta and highlight many of the new features.
>
> Please review for inaccuracies, omissions, and other suggestions /
> errors.
Typo:
"PostgreSQL 16 continues to give users to the ability grant privileged
..."
Should be:
"PostgreSQL 16 continues to give users the ability to grant privileged
..."
Hmmm, upon re-reading that whole sentence (not just my fragment of it
above)
seems pretty unwieldy. A better one isn't springing to mind though. ;)
---
Should this:
"Additionally, starting with release, logical replication ..."
Have the word "this" before "release"?
---
Typo:
"... use the authenticated credentials to connected to other
services."
Should be:
"... use the authenticated credentials to connect to other services."
The sentence after that starts:
"This release also adds ..."
With the one following it starting with "This includes ...". Together,
they a bit unwieldy too. Maybe something like this instead?
"This release also adds several new security-oriented connection
parameters for clients, including ..."
---
Would this:
"You can now also set `sslrootcert` to `system` to specify that
PostgreSQL can use the trusted certificate authority (CA) store
for that operating system."
Be better as?
"You can now also set `sslrootcert` to `system` to instruct
PostgreSQL to use the trusted certificate authority (CA) store
provided by the operating system."
---
Nothing else is jumping out at me. It all seems pretty good. :)
+ Justin
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
2023-05-19 15:02 ` Re: PostgreSQL 16 Beta 1 release announcement draft Justin Clift <[email protected]>
@ 2023-05-21 17:02 ` Jonathan S. Katz <[email protected]>
0 siblings, 0 replies; 9+ messages in thread
From: Jonathan S. Katz @ 2023-05-21 17:02 UTC (permalink / raw)
To: Justin Clift <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
On 5/19/23 11:02 AM, Justin Clift wrote:
> The sentence after that starts:
>
> "This release also adds ..."
>
> With the one following it starting with "This includes ...". Together,
> they a bit unwieldy too. Maybe something like this instead?
Thanks -- I broke this one up into two sentences.
> "This release also adds several new security-oriented connection
> parameters for clients, including ..."
>
> ---
>
> Would this:
>
> "You can now also set `sslrootcert` to `system` to specify that
> PostgreSQL can use the trusted certificate authority (CA) store
> for that operating system."
>
> Be better as?
>
> "You can now also set `sslrootcert` to `system` to instruct
> PostgreSQL to use the trusted certificate authority (CA) store
> provided by the operating system."
>
> ---
I took this suggestion, with modifications.
> Nothing else is jumping out at me. It all seems pretty good. :)
Thanks!
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, 2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
@ 2023-05-20 19:24 ` Cédric Villemain <[email protected]>
2023-05-21 17:04 ` Re: PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
3 siblings, 1 reply; 9+ messages in thread
From: Cédric Villemain @ 2023-05-20 19:24 UTC (permalink / raw)
To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
Hi Jonathan,
> Please review for inaccuracies, omissions, and other suggestions /
> errors.
>
Minor patch attached, with comments.
---
Cédric Villemain +33 (0)6 20 30 22 52
https://Data-Bene.io
PostgreSQL: Expertise - Formation - Développement - Assistance Technique
Attachments:
[text/x-patch] 16beta1.patch (1.6K, 3-16beta1.patch)
download | inline diff:
--- 16beta1.md.orig 2023-05-20 21:12:11.193708177 +0200
+++ 16beta1.md 2023-05-20 21:19:52.954651807 +0200
@@ -61,7 +61,7 @@
### Developer Experience
-PostgreSQL 16 continues to to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
+PostgreSQL 16 continues to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
standard for manipulating [JSON](https://www.postgresql.org/docs/devel/datatype-json.html)
data, including support for SQL/JSON constructors (e.g. `JSON_ARRAY()`,
`JSON_ARRAYAGG()` et al), and identity functions (`IS JSON`). This release also
@@ -84,7 +84,7 @@
These include `pg_maintain`, which enables execution of operations such as
`VACUUM`, `ANALYZE`, `REINDEX`, and others, and `pg_createsubscription`, which
allows users to create a logical replication subscription. Additionally,
-starting with release, logical replication subscribers execute transactions on a
+starting with (this?) release, logical replication subscribers execute transactions on a
table as the table owner, not the superuser.
PostgreSQL 16 now lets you use regular expressions in the [`pg_hba.conf`](https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html)
@@ -126,7 +126,7 @@
### Other Notable Changes
For Windows installations, PostgreSQL 16 now supports a minimum version of
-Windows 10. Additionally, PostgreSQL 16 removes the `promote_trigger_file`
+Windows 10. <!-- Is it on Windows too ? -->Additionally, PostgreSQL 16 removes the `promote_trigger_file`
option to enable the promotion of a standby. Users should use the
`pg_ctl promote` command or `pg_promote()` function to promote a standby.
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
2023-05-20 19:24 ` Re: PostgreSQL 16 Beta 1 release announcement draft Cédric Villemain <[email protected]>
@ 2023-05-21 17:04 ` Jonathan S. Katz <[email protected]>
0 siblings, 0 replies; 9+ messages in thread
From: Jonathan S. Katz @ 2023-05-21 17:04 UTC (permalink / raw)
To: Cédric Villemain <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>
Hi Cédric,
On 5/20/23 3:24 PM, Cédric Villemain wrote:
> Hi Jonathan,
>
>
>> Please review for inaccuracies, omissions, and other suggestions /
>> errors.
>>
> Minor patch attached, with comments.
Thanks -- for these reviews, it's actually easier just to comment in the
email vs. attach a patch, as there are multiple feedback providers and
such the patch may not apply cleanly.
The first two changes had been picked up in previous comments. For the
last change, I understood where the confusion could come from, so I
reordered the sentences.
Thanks,
Jonathan
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, 2-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
@ 2023-05-21 17:06 ` Jonathan S. Katz <[email protected]>
2023-05-24 01:43 ` Re: PostgreSQL 16 Beta 1 release announcement draft Justin Clift <[email protected]>
3 siblings, 1 reply; 9+ messages in thread
From: Jonathan S. Katz @ 2023-05-21 17:06 UTC (permalink / raw)
To: PostgreSQL Advocacy <[email protected]>; +Cc: Michael Alan Brewer <[email protected]>; Cédric Villemain <[email protected]>; Justin Clift <[email protected]>
On 5/19/23 12:18 AM, Jonathan S. Katz wrote:
> Hi,
>
> Attached is a draft of the release announcement for PostgreSQL 16 Beta
> 1. The goal of this announcement is to get people excited about testing
> the beta and highlight many of the new features.
>
> Please review for inaccuracies, omissions, and other suggestions / errors.
>
> Please provide feedback no later than May 24, 0:00 AoE. This will give
> me enough time to incorporate the changes prior to the release the next
> day.
Thanks everyone for your feedback. Here is the updated text that
combines all of the feedback from both -advocacy and -hackers.
Thanks,
Jonathan
The PostgreSQL Global Development Group announces that the first beta release of
PostgreSQL 16 is now [available for download](https://www.postgresql.org/download/).
This release contains previews of all features that will be available when
PostgreSQL 16 is made generally available, though some details of the release
can change during the beta period.
You can find information about all of the features and changes found in
PostgreSQL 16 in the [release notes](https://www.postgresql.org/docs/16/release-16.html):
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 16 on your systems to help us eliminate
bugs or other issues that may exist. While we do not advise you to run
PostgreSQL 16 Beta 1 in production environments, we encourage you to find ways
to run your typical application workloads against this beta release.
Your testing and feedback will help the community ensure that the PostgreSQL 16
release upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our [beta testing process](https://www.postgresql.org/developer/beta/) and how
you can contribute:
[https://www.postgresql.org/developer/beta/](https://www.postgresql.org/developer/beta/)
PostgreSQL 16 Feature Highlights
--------------------------------
### Logical replication enhancements
Logical replication lets PostgreSQL users stream data in real-time to other
PostgreSQL or other external systems that implement the logical protocol. Until
PostgreSQL 16, users could only create logical replication publishers on primary
instances. PostgreSQL 16 adds the ability to perform logical decoding on a
standby instance, giving users more options to distribute their workload, for
example, use a standby that's less busy than a primary to logically replicate
changes.
PostgreSQL 16 also includes several performance improvements to logical
replication. This includes allowing the subscriber to apply large transactions
in parallel, use indexes other than the `PRIMARY KEY` to perform lookups during
`UPDATE` or `DELETE` operations, and allow for tables to be copied using binary
format during initialization.
### Performance
PostgreSQL 16 includes performance improvements in query execution. This release
adds more query parallelism, including allowing `FULL` and `OUTER` joins to
execute in parallel, and parallel execution of the `string_agg` and `array_agg`
aggregate functions. Additionally, PostgreSQL 16 can use incremental sorts in
`SELECT DISTINCT` queries. There are also several optimizations for
[window queries](https://www.postgresql.org/docs/devel/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS),
improvements in lookups for `RANGE` and `LIST` partitions, and support for
"anti-joins" in `RIGHT` and `OUTER` queries.
This release also introduces support for CPU acceleration using SIMD for both
x86 and ARM architectures, including optimizations for processing ASCII and JSON
strings, and array and substransaction searches. Additionally, PostgreSQL 16
introduces [load balancing](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-LOAD-BALANCE-HOSTS)
to libpq, the client library for PostgreSQL.
### Developer Experience
PostgreSQL 16 continues to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
standard for manipulating [JSON](https://www.postgresql.org/docs/devel/datatype-json.html)
data, including support for SQL/JSON constructors (e.g. `JSON_ARRAY()`,
`JSON_ARRAYAGG()` et al), and identity functions (`IS JSON`). This release also
adds the SQL standard [`ANY_VALUE`](https://www.postgresql.org/docs/devel/functions-aggregate.html#id-1.5.8.27.5.2.4.1.1.1.1)
aggregate function, which returns any arbitrary value from the aggregate set.
For convenience, PostgreSQL 16 now lets you specify non-decimal integer
literals, such as `0xff`, `0o777`, and `0b101010`, and use thousands separators,
such as `5_432`.
This release adds support for the extended query protocol to the [`psql`](https://www.postgresql.org/docs/devel/app-psql.html)
client. Users can execute a query, e.g. `SELECT $1 + $2`, and use the
[`\bind`](https://www.postgresql.org/docs/devel/app-psql.html#APP-PSQL-META-COMMAND-BIND)
command to substitute the variables.
### Security features
PostgreSQL 16 continues to give users the ability to grant privileged access to
features without requiring superuser with new
[predefined roles](https://www.postgresql.org/docs/devel/predefined-roles.html).
These include `pg_maintain`, which enables execution of operations such as
`VACUUM`, `ANALYZE`, `REINDEX`, and others, and `pg_create_subscription`, which
allows users to create a logical replication subscription. Additionally,
starting with this release, logical replication subscribers execute transactions
on a table as the table owner, not the superuser.
PostgreSQL 16 now lets you use regular expressions in the [`pg_hba.conf`](https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html)
and [`pg_ident.conf`](https://www.postgresql.org/docs/devel/auth-username-maps.html)
files for matching user and databases names. Additionally, PostgreSQL 16 adds
the ability to include other files in both `pg_hba.conf` and `pg_ident.conf`.
PostgreSQL 16 also adds support for the SQL standard [`SYSTEM_USER`](https://www.postgresql.org/docs/devel/functions-info.html#id-1.5.8.32.3.4.2.2.24.1.1.1)
keyword, which returns the username and authentication method used to establish
a session.
PostgreSQL 16 also adds support for Kerberos credential delegation, which allows
extensions such as `postgres_fdw` and `dblink` to use the authenticated
credentials to connect to other services. This release also adds several new
security-oriented connection parameters for clients. This includes [`require_auth`](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH),
where a client can specify which authentication methods it is willing to accept
from the server. You can now set `sslrootcert` to `system` to instrcut
PostgreSQL to use the trusted certificate authority (CA) store provided by the
client's operating system.
### Operations
PostgreSQL 16 adds several new monitoring features, including the new
[`pg_stat_io`](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW)
view that provides information on I/O statistics. This release also provides a
timestamp for the last time that a [table or index was scanned](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW).
There are also improvements to the normalization algorithm used for
`pg_stat_activity`.
This release includes improvements to the page freezing strategy, which helps
the performance of vacuuming and other maintenance operations. PostgreSQL 16
also improves general support for text collations, which provide rules for how
text is sorted. PostgreSQL 16 sets ICU to be the default collation provider, and
also adds support for the predefined `unicode` and `ucs_basic` collations.
PostgreSQL 16 adds additional compression options to `pg_dump`, including
support for both `lz4` and `zstd` compression.
### Other Notable Changes
PostgreSQL 16 removes the `promote_trigger_file` option to enable the promotion
of a standby. Users should use the `pg_ctl promote` command or `pg_promote()`
function to promote a standby.
PostgreSQL 16 introduced the Meson build system, which will ultimately replace
Autoconf. This release also adds foundational support for developmental features
that will be improved upon in future releases. This includes a developer flag to
enable DirectIO and the ability to use logical replication to bidirectionally
replicate between two tables when `origin=none` is specified in the subscriber.
For Windows installations, PostgreSQL 16 now supports a minimum version of
Windows 10.
Additional Features
-------------------
Many other new features and improvements have been added to PostgreSQL 16. Many
of these may also be helpful for your use cases. Please see the
[release notes](https://www.postgresql.org/docs/16/release-16.html) for a
complete list of new and changed features:
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
Testing for Bugs & Compatibility
--------------------------------
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools in order to
find bugs and regressions before the general availability of PostgreSQL 16. As
this is a Beta, minor changes to database behaviors, feature details, and APIs
are still possible. Your feedback and testing will help determine the final
tweaks on the new features, so please test in the near future. The quality of
user testing helps determine when we can make a final release.
A list of [open issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
is publicly available in the PostgreSQL wiki. You can
[report bugs](https://www.postgresql.org/account/submitbug/) using this form on
the PostgreSQL website:
[https://www.postgresql.org/account/submitbug/](https://www.postgresql.org/account/submitbug/)
Beta Schedule
-------------
This is the first beta release of version 16. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release in late 2023. For further
information please see the [Beta Testing](https://www.postgresql.org/developer/beta/)
page.
Links
-----
* [Download](https://www.postgresql.org/download/)
* [Beta Testing Information](https://www.postgresql.org/developer/beta/)
* [PostgreSQL 16 Beta Release Notes](https://www.postgresql.org/docs/16/release-16.html)
* [PostgreSQL 16 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
* [Submit a Bug](https://www.postgresql.org/account/submitbug/)
Attachments:
[text/plain] 16beta1.md (9.9K, 2-16beta1.md)
download | inline:
The PostgreSQL Global Development Group announces that the first beta release of
PostgreSQL 16 is now [available for download](https://www.postgresql.org/download/).
This release contains previews of all features that will be available when
PostgreSQL 16 is made generally available, though some details of the release
can change during the beta period.
You can find information about all of the features and changes found in
PostgreSQL 16 in the [release notes](https://www.postgresql.org/docs/16/release-16.html):
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 16 on your systems to help us eliminate
bugs or other issues that may exist. While we do not advise you to run
PostgreSQL 16 Beta 1 in production environments, we encourage you to find ways
to run your typical application workloads against this beta release.
Your testing and feedback will help the community ensure that the PostgreSQL 16
release upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our [beta testing process](https://www.postgresql.org/developer/beta/) and how
you can contribute:
[https://www.postgresql.org/developer/beta/](https://www.postgresql.org/developer/beta/)
PostgreSQL 16 Feature Highlights
--------------------------------
### Logical replication enhancements
Logical replication lets PostgreSQL users stream data in real-time to other
PostgreSQL or other external systems that implement the logical protocol. Until
PostgreSQL 16, users could only create logical replication publishers on primary
instances. PostgreSQL 16 adds the ability to perform logical decoding on a
standby instance, giving users more options to distribute their workload, for
example, use a standby that's less busy than a primary to logically replicate
changes.
PostgreSQL 16 also includes several performance improvements to logical
replication. This includes allowing the subscriber to apply large transactions
in parallel, use indexes other than the `PRIMARY KEY` to perform lookups during
`UPDATE` or `DELETE` operations, and allow for tables to be copied using binary
format during initialization.
### Performance
PostgreSQL 16 includes performance improvements in query execution. This release
adds more query parallelism, including allowing `FULL` and `OUTER` joins to
execute in parallel, and parallel execution of the `string_agg` and `array_agg`
aggregate functions. Additionally, PostgreSQL 16 can use incremental sorts in
`SELECT DISTINCT` queries. There are also several optimizations for
[window queries](https://www.postgresql.org/docs/devel/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS),
improvements in lookups for `RANGE` and `LIST` partitions, and support for
"anti-joins" in `RIGHT` and `OUTER` queries.
This release also introduces support for CPU acceleration using SIMD for both
x86 and ARM architectures, including optimizations for processing ASCII and JSON
strings, and array and substransaction searches. Additionally, PostgreSQL 16
introduces [load balancing](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-LOAD-BALANCE-HOSTS)
to libpq, the client library for PostgreSQL.
### Developer Experience
PostgreSQL 16 continues to implement the [SQL/JSON](https://www.postgresql.org/docs/devel/functions-json.html)
standard for manipulating [JSON](https://www.postgresql.org/docs/devel/datatype-json.html)
data, including support for SQL/JSON constructors (e.g. `JSON_ARRAY()`,
`JSON_ARRAYAGG()` et al), and identity functions (`IS JSON`). This release also
adds the SQL standard [`ANY_VALUE`](https://www.postgresql.org/docs/devel/functions-aggregate.html#id-1.5.8.27.5.2.4.1.1.1.1)
aggregate function, which returns any arbitrary value from the aggregate set.
For convenience, PostgreSQL 16 now lets you specify non-decimal integer
literals, such as `0xff`, `0o777`, and `0b101010`, and use thousands separators,
such as `5_432`.
This release adds support for the extended query protocol to the [`psql`](https://www.postgresql.org/docs/devel/app-psql.html)
client. Users can execute a query, e.g. `SELECT $1 + $2`, and use the
[`\bind`](https://www.postgresql.org/docs/devel/app-psql.html#APP-PSQL-META-COMMAND-BIND)
command to substitute the variables.
### Security features
PostgreSQL 16 continues to give users the ability to grant privileged access to
features without requiring superuser with new
[predefined roles](https://www.postgresql.org/docs/devel/predefined-roles.html).
These include `pg_maintain`, which enables execution of operations such as
`VACUUM`, `ANALYZE`, `REINDEX`, and others, and `pg_create_subscription`, which
allows users to create a logical replication subscription. Additionally,
starting with this release, logical replication subscribers execute transactions
on a table as the table owner, not the superuser.
PostgreSQL 16 now lets you use regular expressions in the [`pg_hba.conf`](https://www.postgresql.org/docs/devel/auth-pg-hba-conf.html)
and [`pg_ident.conf`](https://www.postgresql.org/docs/devel/auth-username-maps.html)
files for matching user and databases names. Additionally, PostgreSQL 16 adds
the ability to include other files in both `pg_hba.conf` and `pg_ident.conf`.
PostgreSQL 16 also adds support for the SQL standard [`SYSTEM_USER`](https://www.postgresql.org/docs/devel/functions-info.html#id-1.5.8.32.3.4.2.2.24.1.1.1)
keyword, which returns the username and authentication method used to establish
a session.
PostgreSQL 16 also adds support for Kerberos credential delegation, which allows
extensions such as `postgres_fdw` and `dblink` to use the authenticated
credentials to connect to other services. This release also adds several new
security-oriented connection parameters for clients. This includes [`require_auth`](https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH),
where a client can specify which authentication methods it is willing to accept
from the server. You can now set `sslrootcert` to `system` to instrcut
PostgreSQL to use the trusted certificate authority (CA) store provided by the
client's operating system.
### Operations
PostgreSQL 16 adds several new monitoring features, including the new
[`pg_stat_io`](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW)
view that provides information on I/O statistics. This release also provides a
timestamp for the last time that a [table or index was scanned](https://www.postgresql.org/docs/devel/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW).
There are also improvements to the normalization algorithm used for
`pg_stat_activity`.
This release includes improvements to the page freezing strategy, which helps
the performance of vacuuming and other maintenance operations. PostgreSQL 16
also improves general support for text collations, which provide rules for how
text is sorted. PostgreSQL 16 sets ICU to be the default collation provider, and
also adds support for the predefined `unicode` and `ucs_basic` collations.
PostgreSQL 16 adds additional compression options to `pg_dump`, including
support for both `lz4` and `zstd` compression.
### Other Notable Changes
PostgreSQL 16 removes the `promote_trigger_file` option to enable the promotion
of a standby. Users should use the `pg_ctl promote` command or `pg_promote()`
function to promote a standby.
PostgreSQL 16 introduced the Meson build system, which will ultimately replace
Autoconf. This release also adds foundational support for developmental features
that will be improved upon in future releases. This includes a developer flag to
enable DirectIO and the ability to use logical replication to bidirectionally
replicate between two tables when `origin=none` is specified in the subscriber.
For Windows installations, PostgreSQL 16 now supports a minimum version of
Windows 10.
Additional Features
-------------------
Many other new features and improvements have been added to PostgreSQL 16. Many
of these may also be helpful for your use cases. Please see the
[release notes](https://www.postgresql.org/docs/16/release-16.html) for a
complete list of new and changed features:
[https://www.postgresql.org/docs/16/release-16.html](https://www.postgresql.org/docs/16/release-16.html)
Testing for Bugs & Compatibility
--------------------------------
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools in order to
find bugs and regressions before the general availability of PostgreSQL 16. As
this is a Beta, minor changes to database behaviors, feature details, and APIs
are still possible. Your feedback and testing will help determine the final
tweaks on the new features, so please test in the near future. The quality of
user testing helps determine when we can make a final release.
A list of [open issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
is publicly available in the PostgreSQL wiki. You can
[report bugs](https://www.postgresql.org/account/submitbug/) using this form on
the PostgreSQL website:
[https://www.postgresql.org/account/submitbug/](https://www.postgresql.org/account/submitbug/)
Beta Schedule
-------------
This is the first beta release of version 16. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release in late 2023. For further
information please see the [Beta Testing](https://www.postgresql.org/developer/beta/)
page.
Links
-----
* [Download](https://www.postgresql.org/download/)
* [Beta Testing Information](https://www.postgresql.org/developer/beta/)
* [PostgreSQL 16 Beta Release Notes](https://www.postgresql.org/docs/16/release-16.html)
* [PostgreSQL 16 Open Issues](https://wiki.postgresql.org/wiki/PostgreSQL_16_Open_Items)
* [Submit a Bug](https://www.postgresql.org/account/submitbug/)
[application/pgp-signature] OpenPGP_signature (840B, 3-OpenPGP_signature)
download
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: PostgreSQL 16 Beta 1 release announcement draft
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
2023-05-21 17:06 ` Re: PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
@ 2023-05-24 01:43 ` Justin Clift <[email protected]>
0 siblings, 0 replies; 9+ messages in thread
From: Justin Clift @ 2023-05-24 01:43 UTC (permalink / raw)
To: Jonathan S. Katz <[email protected]>; +Cc: PostgreSQL Advocacy <[email protected]>; Michael Alan Brewer <[email protected]>; Cédric Villemain <[email protected]>
On 2023-05-22 03:06, Jonathan S. Katz wrote:
> On 5/19/23 12:18 AM, Jonathan S. Katz wrote:
>> Hi,
>>
>> Attached is a draft of the release announcement for PostgreSQL 16 Beta
>> 1. The goal of this announcement is to get people excited about
>> testing the beta and highlight many of the new features.
>>
>> Please review for inaccuracies, omissions, and other suggestions /
>> errors.
>>
>> Please provide feedback no later than May 24, 0:00 AoE. This will give
>> me enough time to incorporate the changes prior to the release the
>> next day.
>
> Thanks everyone for your feedback. Here is the updated text that
> combines all of the feedback from both -advocacy and -hackers.
Reading over that, it's pretty good. Well done. :)
+ Justin
^ permalink raw reply [nested|flat] 9+ messages in thread
end of thread, other threads:[~2023-05-24 01:43 UTC | newest]
Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-05-19 04:18 PostgreSQL 16 Beta 1 release announcement draft Jonathan S. Katz <[email protected]>
2023-05-19 14:42 ` Justin Clift <[email protected]>
2023-05-21 16:56 ` Jonathan S. Katz <[email protected]>
2023-05-19 15:02 ` Justin Clift <[email protected]>
2023-05-21 17:02 ` Jonathan S. Katz <[email protected]>
2023-05-20 19:24 ` Cédric Villemain <[email protected]>
2023-05-21 17:04 ` Jonathan S. Katz <[email protected]>
2023-05-21 17:06 ` Jonathan S. Katz <[email protected]>
2023-05-24 01:43 ` Justin Clift <[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