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 01:33:20
Message-ID: AANLkTikdaPcFsxo2ZuJ_j+pDuKuxu19apf7uVC9X+YBQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-15 01:44:29 Re: bg worker: patch 1 of 6 - permanent process
Previous Message Hitoshi Harada 2010-09-15 01:15:12 Re: top-level DML under CTEs