Re: contrib/sslinfo cleanup and OpenSSL errorhandling

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: contrib/sslinfo cleanup and OpenSSL errorhandling
Date: 2020-11-03 09:22:03
Message-ID: 404DEC1F-21D5-47AE-ABED-065427527DB1@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 3 Nov 2020, at 10:05, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> Applied, with the small adjustment of the comma in the docs.

Thanks!

> I wonder if we should perhaps backpatch 0002? The changes to sslinfo
> that were ported go all the way back to 9.6, so it should be a safe
> one I think?

It should be safe given that the code has been in production for a long time.
That being said, sslinfo doesn't have tests (yet) and probably isn't used that
much; perhaps it's best to let this mature in HEAD for a few buildfarm cycles
first?

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2020-11-03 09:22:37 Re: Prefer TG_TABLE_NAME over TG_RELNAME in tests
Previous Message Magnus Hagander 2020-11-03 09:15:48 Re: Move OpenSSL random under USE_OPENSSL_RANDOM