Re: [COMMITTERS] pgsql: In walsender, don't sleep if there's outstanding WAL waiting to

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: In walsender, don't sleep if there's outstanding WAL waiting to
Date: 2010-05-31 10:45:02
Message-ID: 4C03932E.70904@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 31/05/10 13:20, Fujii Masao wrote:
> On Mon, May 31, 2010 at 7:03 PM, Fujii Masao<masao(dot)fujii(at)gmail(dot)com> wrote:
>> This commit seems to have introduced the bug that walsender exits
>> before sending all the WAL up to shutdown checkpoint record when
>> smart shutdown is requested.
>>
>> The attached patch fixes the bug and a tiny typo.
>
> Sorry. I forgot to attach the patch..

Thanks, committed.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2010-05-31 11:11:47 Re: [COMMITTERS] pgsql: Ensure that top level aborts call XLogSetAsyncCommit().
Previous Message Heikki Linnakangas 2010-05-31 10:44:37 pgsql: Send all outstanding WAL before exiting when smart shutdown is

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-05-31 11:11:47 Re: [COMMITTERS] pgsql: Ensure that top level aborts call XLogSetAsyncCommit().
Previous Message Fujii Masao 2010-05-31 10:20:28 Re: [COMMITTERS] pgsql: In walsender, don't sleep if there's outstanding WAL waiting to