Thread: signal and startup process

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,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

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.comPostgreSQL Development, 24x7 Support, Training and Services