Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOmqf-0007j8-Qs for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Jan 2017 14:47:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cOmqf-00020x-Dm for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Jan 2017 14:47:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOmqe-0001yB-GM for pgsql-hackers@postgresql.org; Wed, 04 Jan 2017 14:47:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOmqa-000699-Uj for pgsql-hackers@postgresql.org; Wed, 04 Jan 2017 14:47:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v04ElARp020996; Wed, 4 Jan 2017 09:47:11 -0500 From: Tom Lane To: Magnus Hagander cc: Peter Eisentraut , Michael Paquier , Andreas Karlsson , Michael Banck , Peter Geoghegan , PostgreSQL-development Subject: Re: [PATCH] Reload SSL certificates on SIGHUP In-reply-to: References: <28784.1440554271@sss.pgh.pa.us> <8b967b1e-4bdf-5fd7-9ccb-ce4cfa1d2b3a@proxel.se> <861d27e2-a642-2725-ae31-e375962ab700@proxel.se> <0927799d-9f32-7b40-4fe3-04a281365b7a@proxel.se> <2c1d1551-fd71-113f-7f45-f2379884bf85@proxel.se> <6d45be21-637b-c802-75e7-1ea634ed4089@proxel.se> <05677cd3-63b2-b15b-7afd-798e34e607c7@proxel.se> ! <16e282a4-2573-f629-09e8-e6b0ac615890@2ndquadrant.com> <29982.1483412575@sss.pgh.pa.us> <23913.1483458895@sss.pgh.pa.us> Comments: In-reply-to Magnus Hagander message dated "Wed, 04 Jan 2017 14:46:11 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20994.1483541230.1@sss.pgh.pa.us> Date: Wed, 04 Jan 2017 09:47:10 -0500 Message-ID: <20995.1483541230@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Magnus Hagander writes: > On Tue, Jan 3, 2017 at 4:54 PM, Tom Lane wrote: >> I think probably the right thing for now is to install a do-nothing >> callback, so that at least we don't have the issue of the postmaster >> freezing at SIGHUP. If someone feels like trying to revive support >> of passphrase-protected server keys, that would be a perfectly fine >> base to build on; they'd need a callback there anyway. > Does it still support passphrase protected ones on startup, or did that get > thrown out with the bathwater? It does not; what would be the point, if the key would be lost at SIGHUP? > I think that's definitely a separate thing > and there are a nontrivial number of people who would be interested in a > setup where they can use a passphrase to protect it initially, just not > reload it. If any of those number of people want to step up and design/implement a non-broken solution for passphrases, that'd be fine with me. But I would want to see something that's actually a credible solution, allowing the postmaster to be started as a normal daemon. And working on Windows. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers