Re: [HACKERS] PostgreSQL not setting OpenSSL session id context? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] PostgreSQL not setting OpenSSL session id context?
Date
Msg-id 20170804042705.o52qife3x5nuxyr3@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] PostgreSQL not setting OpenSSL session id context?  (Shay Rojansky <roji@roji.org>)
Responses Re: [HACKERS] PostgreSQL not setting OpenSSL session id context?  (Shay Rojansky <roji@roji.org>)
List pgsql-hackers
On 2017-08-04 07:22:42 +0300, Shay Rojansky wrote:
> I'm still not convinced of the risk/problem of simply setting the session
> id context as I explained above (rather than disabling the optimization),
> but of course either solution resolves my problem.

How would that do anything? Each backend has it's own local
memory. I.e. any cache state that openssl would maintain wouldn't be
useful. If you want to take advantage of features around this you really
need to cache tickets in shared memory...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Shay Rojansky
Date:
Subject: Re: [HACKERS] PostgreSQL not setting OpenSSL session id context?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] PostgreSQL not setting OpenSSL session id context?