From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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:51:47 |
Message-ID: | 200111160451.fAG4pl306516@candle.pha.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.
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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-11-16 05:26:40 | Re: [HACKERS] bug or change in functionality in 7.2? |
Previous Message | Tom Lane | 2001-11-16 04:42:35 | Re: 7.2 pg_hba.conf load on SIGHUP? |