| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIGHUP during recovery |
| Date: | 2009-03-04 13:58:21 |
| Message-ID: | 49AE88FD.4010907@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii Masao wrote:
> 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).
Thanks, committed.
The fact that bgwriter can run simultaneously with the startup process
makes this more important than before. Otherwise if you change something
like log_line_prefix, bgwriter will use the new setting but startup
process will not.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Tolley | 2009-03-04 14:19:55 | Re: Make SIGHUP less painful if pg_hba.conf is not readable |
| Previous Message | Peter Eisentraut | 2009-03-04 13:26:36 | Re: SQL/MED compatible connection manager |