| From: | Doug McNaught <doug(at)wireboard(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, David Ford <david(at)blue-labs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: best method of reloading pg_hba.conf |
| Date: | 2001-11-09 23:50:42 |
| Message-ID: | m3g07nqzal.fsf@belphigor.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-09 23:55:54 | Re: best method of reloading pg_hba.conf |
| Previous Message | Bruce Momjian | 2001-11-09 23:46:14 | Re: best method of reloading pg_hba.conf |