Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml
Date
Msg-id Pine.LNX.4.30.0111031822050.607-100000@peter.localdomain
Whole thread Raw
In response to Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml oc/src/sgm ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml oc/src/sgm ...
List pgsql-hackers
Tom Lane writes:

> > Tom, does a client do a kill() to its parent on password change?
>
> Right, it's basically the same as the way we handle checkpoint and
> SI-overrun signaling:
>
>     /*
>      * Signal the postmaster to reload its password-file cache.
>      */
>     if (IsUnderPostmaster)
>         kill(getppid(), SIGHUP);

But does this mean that postgresql.conf will be reread globally (i.e., by
the postmaster), when the user signals HUP only to a single backend?  I
guess this is actually a good idea, but it would be a change of
functionality.  Admittedly, the window of utility of signalling only a
single backend is small, but let's make sure the hupping behavior is
correctly documented, because this is possibly not expected.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Licensing issues including another projects source
Next
From: "Dave Cramer"
Date:
Subject: Re: Licensing issues including another projects source code into the jdbc driver