Re: pgsql: Remove support for OpenSSL 0.9.8 and 1.0.0

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Remove support for OpenSSL 0.9.8 and 1.0.0
Date: 2020-01-06 06:48:02
Message-ID: CAD5tBc+yihutcfg561xmc3n6+_SqOBNkZ1QRkZEKcTjP-VXaQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Jan 6, 2020 at 3:50 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Mon, Jan 06, 2020 at 12:06:30AM -0500, Tom Lane wrote:
> > As I recall, we'd already decided that nightjar needs to be EOL'd
> > because that version of FreeBSD has nonatomic file rename [1].
>
> Ah, indeed. I forgot this discussion, and that was not long ago.
>
>
>

I was going to upgrade it when I could migrate the OS of the host machine
to CentOS 8. However, last time I looked some things about Centos 8 (e.g.
EPEL) were not mature enough. In any case, to do that requires my physical
presence, and I'm currently 10,000 miles or so away from it until mid
March. I'll turn off both nightjar and friarbird in the meantime.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2020-01-06 07:51:24 pgsql: Have logical replication subscriber fire column triggers
Previous Message Michael Paquier 2020-01-06 05:20:22 Re: pgsql: Remove support for OpenSSL 0.9.8 and 1.0.0