From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(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:19:16 |
Message-ID: | 1284531556.1952.4734.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2010-09-15 at 10:33 +0900, Fujii Masao wrote:
> On Wed, Sep 15, 2010 at 12:14 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> >
> > Like latches, nice one.
> >
> > The way the loop in WalSender now happens it won't send any outstanding
> > WAL if a shutdown is requested while it is waiting.
> >
> > That probably needs to change and we'd do similarly in other procs.
>
> Really? ISTM that walsender tries to send all outstanding WAL without
> problems after it receives SIGUSR2. Am I missing something?
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);
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2010-09-15 06:38:09 | Re: Latches, loop and exit |
Previous Message | SAKAMOTO Masahiko | 2010-09-15 05:46:24 | patch: SQL/MED(FDW) DDL |