| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIGHUP during recovery |
| Date: | 2009-03-05 09:28:21 |
| Message-ID: | 1236245301.31880.137.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-03-04 at 15:58 +0200, Heikki Linnakangas wrote:
> 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.
Should we reload recovery.conf also?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2009-03-05 09:48:11 | Re: building pg_dump doesn't work |
| Previous Message | Martin Pihlak | 2009-03-05 08:59:38 | Re: SQL/MED compatible connection manager |