Hi Michael and Peter,
Thanks a lot for the elaboration of the patch process for PG17. It's
really unfortunate missing the the development cycle of PG17.
Just some context of why we hurry to try to catch up with PG17.
There are certain government, financial and other enterprise organizations that
have very strict requirements about the encrypted communication and more
specifically about fine grained params like the TLS ciphers and curves that
they use. The default ones for those customers are not acceptable. Any products
that integrate Postgres and requires encrypted communication with the Postgres
would have to fulfil those requirements.
So if we can have this patch in the upcoming new major version, that means
Postgres users who have similar requirements can upgrade to PG17.
Thanks!
Original Email
Sender:"Michael Paquier"< [email protected] >;
Sent Time:2024/6/7 18:46
To:"Erica Zhang"< [email protected] >;
Cc recipient:"Peter Eisentraut"< [email protected] >;"pgsql-hackers"<
[email protected] >;
Subject:Re: Re: Add support to TLS 1.3 cipher suites and curves lists
On Fri, Jun 07, 2024 at 06:02:37PM +0800, Erica Zhang wrote:
> I see the https://commitfest.postgresql.org/48/ is still open, could
> it be possible to target for PG17? As I know PG17 is going to be
> release this year so that we can upgrade our instances to this new
> version accodingly.
Echoing with Peter, https://commitfest.postgresql.org/48/ is planned
to be the first commit fest of the development cycle for Postgres 18.
v17 is in feature freeze state and beta, where only bug fixes are
accepted, and not new features.
--
Michael
