Message-ID: <55DE47F6.5000108@proxel.se>
Date: Thu, 27 Aug 2015 01:12:54 +0200
From: Andreas Karlsson <andreas@proxel.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Peter Eisentraut <peter_e@gmx.net>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP
References: <556A6E8A.9030400@proxel.se> <55956342.9050408@gmx.net>
 <55AEE95E.7090304@proxel.se> <55B82208.4090901@gmx.net>
 <8917.1438133076@sss.pgh.pa.us> <55BAA50E.5040908@proxel.se>
 <28784.1440554271@sss.pgh.pa.us>
In-Reply-To: <28784.1440554271@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 08/26/2015 03:57 AM, Tom Lane wrote:
> Is it unreasonable of me to ask for the Windows behavior to be fixed at
> the same time?  I dunno.  It's perhaps less broken than the Unix behavior,
> but that doesn't make it desirable.  OTOH it might be a significantly
> larger patch, and I confess I'm not even too sure what we'd have to do.
>
> So I think the way to move this forward is to investigate how to hold
> the SSL config constant until SIGHUP in an EXEC_BACKEND build.  If we
> find out that that's unreasonably difficult, maybe we'll decide that
> we can live without it; but I'd like to see the question investigated
> rather than ignored.

I think this is a real concern and one that I will look into, to see if 
it can be fixed with a reasonable amount of work.

Andreas


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers