Re: Unnecessary connection overhead due copy-on-write (mainly openssl)
От | Jacob Champion |
---|---|
Тема | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) |
Дата | |
Msg-id | CAOYmi+nsgM0+NExR256QW+5da6VhPdr8TO15Wte=k3R5a6JQ8w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Unnecessary connection overhead due copy-on-write (mainly openssl) (Peter Eisentraut <peter@eisentraut.org>) |
Ответы |
Re: Unnecessary connection overhead due copy-on-write (mainly openssl)
Re: Unnecessary connection overhead due copy-on-write (mainly openssl) Re: Unnecessary connection overhead due copy-on-write (mainly openssl) |
Список | pgsql-hackers |
On Fri, Jun 6, 2025 at 4:56 AM Peter Eisentraut <peter@eisentraut.org> wrote: > It seems weird to me that openssl spends so much effort tidying up its > memory allocations just before exiting. We could just skip that. > Looking through the code of OPENSSL_cleanup(), there might be one or two > cases of log or trace files that get flushed during cleanup, so it's not > an absolute no-brainer to skip all the cleanup. 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". But that's pure FUD and guesswork; I have no examples to point to, so there might not be any providers that need that. --Jacob
В списке pgsql-hackers по дате отправления: