| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2021-09-25 18:34:44 |
| Message-ID: | 9646ED6D-7429-4A7E-A9FD-E4466084C551@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Sep 2021, at 15:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>>> On 25 Sep 2021, at 12:03, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>>> As 9.6 will be EOL'd in a couple of weeks, is that really
>>> worth the effort though? It sounds risky to me to introduce an
>>> invasive change as that would increase the risk of bugs for existing
>>> users. So my vote would be to just let this one go.
>
>> Agreed, if it's not a simple fix it's unlikely to be worth it.
>
> Yeah, there will be no second chance to get 9.6.last right,
> so I'd vote against touching it for this.
Fair point. Should we perhaps instead include a note in the pgcrypto docs for
9.6 that 3.0.0 isn't supported and leave it at that?
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2021-09-25 19:27:10 | Re: extended stats on partitioned tables |
| Previous Message | Mark Dilger | 2021-09-25 18:04:29 | Re: Fixing WAL instability in various TAP tests |