Re: re-reading SSL certificates during server reload

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alexey Klyukin <alexk(at)hintbits(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: re-reading SSL certificates during server reload
Date: 2014-08-28 14:12:19
Message-ID: 25092.1409235139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Aug 28, 2014 at 4:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Why would they need to be BACKEND, as opposed to just PGC_SIGHUP?

> I just thought semantically - because they do not change in a running
> backend. Any running backend will continue with encryption set up
> based on the old certificate.

Hm. Yeah, I guess there is some use in holding onto the values that were
actually used to initialize the current session, or at least there would
be if we exposed the cert contents in any fashion.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-08-28 14:14:53 Re: [COMMITTERS] pgsql: Allow units to be specified in relation option setting value.
Previous Message Michael Paquier 2014-08-28 14:10:09 Re: pgsql: Allow units to be specified in relation option setting value.