From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove support for OpenSSL 0.9.8 and 1.0.0
In-reply-to: <18698.1578287190@sss.pgh.pa.us>
References: <E1ioJS0-0005f9-7G@gemulon.postgresql.org>
 <20200106045858.GJ3598@paquier.xyz> <18698.1578287190@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 06 Jan 2020 00:06:30 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <31056.1578341305.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 06 Jan 2020 15:08:25 -0500
Message-ID: <31057.1578341305@sss.pgh.pa.us>
Precedence: bulk

I wrote:
> You'll probably see failures from some of my dinosaurs too.
> I've not yet switched them over to using newer OpenSSL,
> but will do so tomorrow or so.

I updated prairiedog and gaur to use OpenSSL 1.0.1e, but we are
not out of the woods there:

* prairiedog required 6:46 to run the ssl test [1], compared to 3:24
in its last run with 0.9.8x.  Why so much slower?

* gaur fell over in the ssl test [2].  I had not asked it to run that
test before, so this may well be a pre-existing issue not something
new with the version change.  It looks like something in that test
is assuming that we have IPv6 support, which maybe it shouldn't be,
even in 2020.

			regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dprairiedog&d=
t=3D2020-01-06%2015%3A25%3A37
[2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dgaur&dt=3D20=
20-01-06%2015%3A47%3A18