From: | Nico Williams <nico(at)cryptonector(dot)com> |
---|---|
To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) |
Date: | 2025-06-06 16:25:46 |
Message-ID: | aEMWiu1XLtU4HTyZ@ubby |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 06, 2025 at 08:41:20AM -0700, Jacob Champion wrote:
> I guess I'd be concerned that a hardware crypto provider might need
> good-faith cleanup to work well. I understand they can't rely on
> atexit in general, but there would be a big difference between "you
> might have to clean up after a crash" and "every single connection
> litters the hardware with unused stuff".
I'd expect all subsystems to recover cleanly from unclean shutdowns. I
know, that's a lot to expect, but nowadays pretty much all filesystems
used in production do, for example.
> But that's pure FUD and guesswork; I have no examples to point to, so
> there might not be any providers that need that.
I doubt that PG w/ OpenSSL in any configuration maintains stateful
interactions with HW cryptographic providers.
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2025-06-06 16:33:36 | Re: CHECKPOINT unlogged data |
Previous Message | Christoph Berg | 2025-06-06 16:20:21 | Re: CHECKPOINT unlogged data |