Re: Re: pg_hba.conf pre-parsing change

On Tuesday 31 July 2001 19:20, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > We could, but we don't with postgresql.conf so it made sense to keep the
> > behavior the same for the two files.

> I'm inclined to agree --- for one thing, this allows one to edit the
> files in place without worrying that the postmaster will pick up a
> partially-edited file. But I wanted to throw the issue out to pghackers
> to see if anyone would be really unhappy about having to SIGHUP the
> postmaster after changing the authorization conf files.

Hmmm...

I much prefer having to SIGHUP postmaster -- that is semistandard daemon
behavior, no? If enough people want the other behavior, add a
postgresql.conf setting to activate 'modification notification' for config
files.

If nothing else, an 'accidental' pg_hba.conf corruption, deletion, or
malicious change has to have a 'confirmation' step before a running
postmaster sees the changes.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11