Re: Latches, loop and exit

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <heikki(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Latches, loop and exit
Date: 2010-09-15 06:38:09
Message-ID: AANLkTimyraBazJ3jNjTwTbnYkttDH3bt_rPT=tVT50ga@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 15, 2010 at 3:19 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> For SIGUSR2, you're right.
>
> However, if the following clause is ever invoked, then the loop does
> have problems and we leave when not caught up.
>
> if (!PostmasterIsAlive(true))
>        exit(1);

In normal shutdown case, that clause is not invoked since postmaster
exits after walsender exits. That is, the clause is for emergency case,
e.g., case where SIGKILL arrives at postmaster. Even in such an
emergency case, you think walsender should send all outstanding WAL?

Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-09-15 06:40:40 Re: Latches, loop and exit
Previous Message Simon Riggs 2010-09-15 06:19:16 Re: Latches, loop and exit