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
Date: Mon, 06 Jan 2020 15:08:25 -0500
Message-ID: <31057.1578341305@sss.pgh.pa.us> (raw)
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>
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=prairiedog&dt=2020-01-06%2015%3A25%3A37
[2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gaur&dt=2020-01-06%2015%3A47%3A18
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-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove support for OpenSSL 0.9.8 and 1.0.0
In-Reply-To: <31057.1578341305@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