> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >> Will a HUP cause the child postgres processes to restart as well?
> >> What if a transaction is occuring at the time of the HUP?
>
> > Again, no effect on children of postmaster.
>
> Not so. The postmaster responds to the signal as soon as it's idle,
> rereads the conf file itself, and rebroadcasts SIGHUP to all its
> children. The children then reread the conf file immediately after they
> next receive a query from their clients. See postmaster/postmaster.c
> and tcop/postgres.c.
>
> A lot of the configuration file entries are not allowed to change in a
> running backend, so the children will ignore attempted changes in those
> entries. But for entries that can be changed on the fly, the response
> is reasonably prompt across the board.
Yes, true. The specific question was about pg_hba.conf, which only
affects the postmaster. postgresql.conf is a file read by postmastger
and backends, and that is re-read by children on sighup.
--
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
