| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) |
| Date: | 2025-06-06 18:58:46 |
| Message-ID: | CAOYmi+nki8O-tpD8tQUYw1YCxCXEmmt51QXj3e-bd3tr8ezKhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 6, 2025 at 9:37 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> It's not just crashes, e.g. the startup packet timeout is also handled by
> _exit() - and it can be triggered remotely.
Fair point...
> ISTM that if crypto providers
> can't handle _exit(), we have a bigger problem.
...so I guess I need to figure out whether we have a bigger problem. I
hope we don't.
Note that OpenSSL seems to be interested in removing the atexit()
handling altogether, and requiring applications to manually call the
cleanup function, in 4.0. [1]
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-06-06 19:21:13 | Re: Non-reproducible AIO failure |
| Previous Message | Jacob Champion | 2025-06-06 18:58:38 | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) |