pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Update minimum SSL version
Date: Wed, 04 Dec 2019 07:53:21 -0500
Message-ID: <12313.1575464001@sss.pgh.pa.us> (raw)
In-Reply-To: <6d3b7b69-0970-4d40-671a-268c46e93fe3@2ndquadrant.com>
References: <CABUevEy4meLCVnrTbjU9zoJvRoWUjvmdmUUkaoAqKYkk0MWHYA@mail.gmail.com>
	<20191129125727.GN2505@paquier.xyz>
	<13786.1575041447@sss.pgh.pa.us>
	<20191130024345.GD99291@paquier.xyz>
	<CA+TgmobM7j=+NN+juu9=urfw0-Bt22QvDdxaPW8O-KK5yegADQ@mail.gmail.com>
	<929.1575304768@sss.pgh.pa.us>
	<CA+TgmoY4E8J3id=0xJW9m3vLwdLaOoYefj334nZpLx26T-XftA@mail.gmail.com>
	<4448.1575309086@sss.pgh.pa.us>
	<20191203035323.GB1634@paquier.xyz>
	<CABUevEyNhpHpH3UCxJ8B5nm9dHtxQStj8=yVu+BWYNd84AoQ0g@mail.gmail.com>
	<20191203110854.GG1634@paquier.xyz>
	<CABUevEyxxFb1CL_V1knnV65O6tK_EGJOysfSXz1o-a-LanOs7Q@mail.gmail.com>
	<6d3b7b69-0970-4d40-671a-268c46e93fe3@2ndquadrant.com>

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2019-12-03 12:44, Magnus Hagander wrote:
>> On Tue, Dec 3, 2019 at 12:09 PM Michael Paquier <michael@paquier.xyz 
>> <mailto:michael@paquier.xyz>> wrote:
>> On Tue, Dec 03, 2019 at 10:10:57AM +0100, Magnus Hagander wrote:
>>> Is 1.0.1 considered a separate major from 1.0.0, in this reasoning? Because
>>> while retiring 1.0.0 should probably not be that terrible, 1.0.1
>>> is still in very widespread use on most long term supported distributions.

> This would mean we'd stop support for RHEL 5, which is probably OK, 
> seeing that even the super-extended support ends in November 2020.

> Dropping RHEL 5 would also allow us to drop support for Python 2.4, 
> which is something I've been itching to do. ;-)

> In both of these cases, maintaining support for all these ancient 
> versions is a significant burden IMO, so it would be good to clean up 
> the tail end a bit.

So, what exactly are we going to set as the new minimum version in
each case?  I'll have to go update my trailing-edge-Johnnie buildfarm
critters, and it'd make sense to have them continue to test the
oldest nominally-supported versions.

For OpenSSL it seems like 1.0.1a is the target, per the above
discussion.

For Python, I'll just observe that RHEL6 ships 2.6.6, so we can't
bump up to 2.7.

			regards, tom lane





view thread (38+ messages)  latest in thread

Message-ID: <12313.1575464001@sss.pgh.pa.us>
Permalink:  ../12313.1575464001@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12313.1575464001@sss.pgh.pa.us

 · 

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: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, magnus@hagander.net, michael@paquier.xyz, robertmhaas@gmail.com, daniel@yesql.se
  Subject: Re: Update minimum SSL version
  In-Reply-To: <12313.1575464001@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox