Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Peter Eisentraut <peter@eisentraut.org>

Cc: Daniel Gustafsson <daniel@yesql.se>, Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, mikael.kjellstrom@gmail.com, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2024-04-19T05:37:35Z

Lists: pgsql-hackers

On Thu, Apr 18, 2024 at 12:53:43PM +0200, Peter Eisentraut wrote:
> If everything is addressed, I agree that 0001, 0003, and 0004 can go into
> PG17, the rest later.

About the PG17 bits, would you agree about a backpatch?  Or perhaps
you disagree?
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Remove obsolete unconstify()
- 1fb2308e698e 18.0 landed
Only perform pg_strong_random init when required
- c3333dbc0c0f 18.0 landed
Remove support for OpenSSL older than 1.1.0
- a70e01d4306f 18.0 landed
Support SSL_R_VERSION_TOO_LOW when using LibreSSL
- d80f2ce29465 17.0 landed
Support disallowing SSL renegotiation when using LibreSSL
- 44e27f0a6d07 17.0 landed
Doc: Use past tense for things which happened in the past
- 91d6429fad55 17.0 landed
Remove support for OpenSSL 1.0.1
- 8e278b657664 17.0 landed
Remove support for OpenSSL 0.9.8 and 1.0.0
- 7b283d0e1d1d 13.0 cited