Re: best method of reloading pg_hba.conf - Mailing list pgsql-hackers

From Doug McNaught
Subject Re: best method of reloading pg_hba.conf
Date
Msg-id m3g07nqzal.fsf@belphigor.mcnaught.org
Whole thread Raw
In response to Re: best method of reloading pg_hba.conf  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Hannu Krosing <hannu@tm.ee> writes:

> Bruce Momjian wrote:
> > 
> > > Is the best method of reloading pg_hba.conf to SIGHUP the master process?
> > 
> > In 7.2, yes, pg_ctl restart or SIGHUP.  On 7.1.X pg_hba.conf is reread
> > on every connection request.
> 
> Why was it changed ?

I think to give the admin control over when it gets reread.  Say it's
being automatically generated by a cron job for some reason, and a
connection request comes in while it's being written--the backend
would get a corrupted version of the file.  (Or if a text editor's in
the midst of saving it).

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.  --T. J. Jackson, 1863


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: best method of reloading pg_hba.conf
Next
From: Tom Lane
Date:
Subject: Re: Bug?? -- Alter table drop constraint doesn't seem to work on a primary key constraint in 7.2beta2