| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: signal and startup process |
| Date: | 2010-10-14 18:17:58 |
| Message-ID: | 1287080278.1725.1092.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Committed.
On Thu, 2010-10-14 at 12:57 +0900, Fujii Masao wrote:
> Hi,
>
> It takes nonsensically extra several seconds to shut down the standby server.
> This is because the startup process cannot respond immediately the SIGTERM
> signal sent by postmaster for the shutdown while it's sleeping on WaitLatch.
> This delays the shutdown for up to the sleep time on WaitLatch (currently
> 5 seconds).
>
> The signal handlers of the startup process should call SetLatch to respond
> the signals even while it's sleeping on WaitLatch, like those of walsender
> already do. The attached patch does this.
>
> Regards,
>
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-10-14 18:33:24 | Re: [HACKERS] Docs for archive_cleanup_command are poor |
| Previous Message | Simon Riggs | 2010-10-14 18:17:35 | Re: Bug in writeTimeLineHistory |