Re: improve ssl error code, 2147483650 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: improve ssl error code, 2147483650
Date
Msg-id 683078.1709858768@sss.pgh.pa.us
Whole thread Raw
In response to Re: improve ssl error code, 2147483650  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: improve ssl error code, 2147483650
List pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes:
> On 7 Mar 2024, at 20:58, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> This could probably do with a comment, and we need to propagate
>> the fix into libpq's copy of the function too.  Barring objections,
>> I'll take care of that and push it later today.

> LGTM.

Done so far as be-secure-openssl.c and fe-secure-openssl.c are
concerned.  But I noticed that src/common/cryptohash_openssl.c and
src/common/hmac_openssl.c have their own, rather half-baked versions
of SSLerrmessage.  I didn't do anything about that in the initial
patch, because it's not clear to me that those routines would ever
see system-errno-based errors, plus their comments claim that
returning NULL isn't terribly bad.  But if we want to do something
about it, I don't think that maintaining 3 copies of the code is the
way to go.  Maybe push be-secure-openssl.c's version into src/common?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Sutou Kouhei
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations
Next
From: Melanie Plageman
Date:
Subject: Re: Confine vacuum skip logic to lazy_scan_skip