| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Command Prompt, Inc(dot)" <pgsql-general(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.2 pg_hba.conf load on SIGHUP? |
| Date: | 2001-11-16 04:42:35 |
| Message-ID: | 22926.1005885755@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-11-16 04:51:47 | Re: 7.2 pg_hba.conf load on SIGHUP? |
| Previous Message | Christopher Kings-Lynne | 2001-11-16 02:58:06 | Re: bug or change in functionality in 7.2? |