| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Abhishek Chanda <abhishek(dot)becs(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding support for SSLKEYLOGFILE in the frontend |
| Date: | 2025-03-20 16:58:47 |
| Message-ID: | CAOYmi+mPLa=MJ8WGmAKizkm71QE04GDqdo2py2aRwu76pG+JTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 20, 2025 at 3:58 AM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>
> I'm not sure if openssl has some locking on it,
OpenSSL leaves it up to the application (us). OpenSSL 3.5 will
apparently add a builtin implementation, which from a quick skim does
use locking. As another datapoint, libcurl's implementation appears to
rely on implicit flockfile().
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-03-20 16:58:56 | Re: Adding support for SSLKEYLOGFILE in the frontend |
| Previous Message | Mahendra Singh Thalor | 2025-03-20 16:43:56 | Re: change on_exit_nicely_list array to the dynamic array to increase slots at run time for pg_restore |