| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Carla Iriberri <ciriberri(at)salesforce(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: could not accept SSL connection: Success |
| Date: | 2022-01-19 20:05:35 |
| Message-ID: | CA+hUKGLdXHZOss7f2zgF+a9U2CakyYVgPQuOY48wZVSVyUK15Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 20, 2022 at 12:06 AM Carla Iriberri
<ciriberri(at)salesforce(dot)com> wrote:
> On Wed, Jan 19, 2022 at 5:42 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> "On an unexpected EOF, versions before OpenSSL 3.0 returned
>> SSL_ERROR_SYSCALL, nothing was added to the error stack, and errno was
>> 0. Since OpenSSL 3.0 the returned error is SSL_ERROR_SSL with a
>> meaningful error on the error stack."
> Thanks, Michael, that's it, indeed! I had missed that part of the
> OpenSSL docs. These PG instances are running on Ubuntu Focal hosts that come
> with OpenSSL 1.1.1.
Good news, I'm glad they nailed that down. I recall that this
behaviour was a bit of a moving target in earlier versions:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2022-01-19 21:25:59 | Re: WAL Archiving and base backup |
| Previous Message | Garfield Lewis | 2022-01-19 19:38:52 | Can we get the CTID value |