best method of reloading pg_hba.conf

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.

-- 
  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, Pennsylvania 19026

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