| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2021-08-10 13:27:18 |
| Message-ID: | ADF19C83-A163-4C0C-B197-61922799ABA8@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 6 Aug 2021, at 21:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> Until there is an animal running OpenSSL 3.0.0 in the buildfarm I think this
>> should be HEAD only. Further down the line we need to support OpenSSL 3 in all
>> backbranches IMO since they are all equally likely to be compiled against it,
>> but not until we can regularly test against it in the farm.
>
> Works for me.
These have now been committed, when OpenSSL 3.0.0 ships and there is coverage
in the buildfarm I’ll revisit this for the backbranches.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-08-10 13:27:33 | Re: Autovacuum on partitioned table (autoanalyze) |
| Previous Message | Greg Nancarrow | 2021-08-10 13:27:14 | Re: Skipping logical replication transactions on subscriber side |