| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposed WAL changes |
| Date: | 2001-03-07 16:57:42 |
| Message-ID: | Pine.LNX.4.30.0103071755120.986-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Do I have to send SIGHUP after changing postgresql.conf ?
>
> In general, yes. I think that for the (still vaporware) archdir option,
> you might not need to: archdir will only be looked at by the checkpoint
> subprocess, and I think that a newly spawned backend will reread
> postgresql.conf anyway. Peter, is that correct?
Nope. The configuration file is only read at postmaster start and after
SIGHUP. If any starting backend would read it automatically, the admin
could never be sure about his edits.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lance Taylor | 2001-03-07 17:37:49 | Re: Proposed WAL changes |
| Previous Message | The Hermit Hacker | 2001-03-07 16:57:02 | Re: Proposed WAL changes |