| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | SIGHUP during recovery |
| Date: | 2009-03-03 07:17:06 |
| Message-ID: | 3f0b79eb0903022317t77f7dbacm7bb6210a68df4c3f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Currently, the startup process ignores SIGHUP.
The attached patch allows the startup process to re-read config file:
when SIGHUP arrives, the startup process also receives the signal
from postmaster and reload the settings in main redo apply loop.
Obviously, this is useful to change the parameters which the startup
process may use (e.g. log_line_prefix, log_checkpoints).
Any comments welcome.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| sighup_startup_0303.patch | application/octet-stream | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KaiGai Kohei | 2009-03-03 07:39:30 | Updates of SE-PostgreSQL 8.4devel patches (r1668) |
| Previous Message | ITAGAKI Takahiro | 2009-03-03 06:52:22 | Why do we keep UnusedLock1 in LWLockId? |