Re: Fix for OpenSSL error queue bug - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Fix for OpenSSL error queue bug
Date
Msg-id CAM3SWZTxa4a-CCJJiDipt6n6Z5Sorm0LOt6R986oySg0D2WY9A@mail.gmail.com
Whole thread Raw
In response to Re: Fix for OpenSSL error queue bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fix for OpenSSL error queue bug
List pgsql-hackers
On Mon, Mar 14, 2016 at 4:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So your proposal is basically to do #2 in all branches?  I won't fight it,
> if it doesn't bloat the code much.  The overhead should surely be trivial
> compared to network communication costs, and I'm afraid you might be right
> about the risk of latent bugs.

Yes, with one small difference: I wouldn't be calling ERR_get_error()
in the common case where SSL_get_error() returns SSL_ERROR_NONE, on
the theory that skipping that case represents no risk. I'm making a
concession to Peter E's view that that will calling ERR_get_error()
more will add useless cycles.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Timeline following for logical slots
Next
From: Robbie Harwood
Date:
Subject: [PATCH v7] GSSAPI encryption support