Re: re-reading SSL certificates during server reload
От | Andres Freund |
---|---|
Тема | Re: re-reading SSL certificates during server reload |
Дата | |
Msg-id | 20140828143416.GG25984@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: re-reading SSL certificates during server reload (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 2014-08-28 10:30:30 -0400, Tom Lane wrote: > Andres Freund <andres@2ndquadrant.com> writes: > > On 2014-08-28 10:20:08 -0400, Tom Lane wrote: > >> Having said that, there's a nearby thread about inventing a "SUBACKEND" > >> GUC category, and that's likely what we'd really want to use here, just > >> on the grounds that superusers would know better. > > > What we really want is PGC_SIGHUP | PGC_BACKEND, right? > > How you figure that? You *don't* want it to change at SIGHUP, at least > not in existing sessions. And the postmaster already thinks it should > reload PGC_BACKEND variables on SIGHUP. Well, it shouldn't be settable at connection start but changed for new connections (expressed by _SIGHUP). But it shouldn't change for existing connections (therefor PGC_BACKEND). Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: