Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml oc/src/sgm ...

> CVSROOT:    /cvsroot
> Module name:    pgsql
> Changes by:    tgl@postgresql.org    01/11/02 13:39:57
> 
> Modified files:
>     doc/src/sgml   : client-auth.sgml runtime.sgml 
>     src/backend/commands: user.c 
>     src/backend/libpq: crypt.c 
>     src/backend/postmaster: postmaster.c 
>     src/include/libpq: crypt.h 
> 
> Log message:
>     Fix pg_pwd caching mechanism, which was broken by changes to fork
>     postmaster children before client auth step.  Postmaster now rereads
>     pg_pwd on receipt of SIGHUP, the same way that pg_hba.conf is handled.
>     No cycles need be expended to validate password cache validity during
>     connection startup.

Tom, does a client do a kill() to its parent on password change?

If this is true, people can't depend on editing pg_hba.conf and having
the change take affect _only_ when they sighup the postmaster.  If
someone changes a password, pg_hba.conf gets reread anyway, right?  Not
a problem but something we should be aware of.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026