Re: pgsql: Fix assertion failure by an immediate shutdown.

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Fujii Masao <fujii(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix assertion failure by an immediate shutdown.
Date: 2013-08-07 18:07:01
Message-ID: CAHGQGwF2w-2NZpqK6D49J8=nzfubZTqwtSZvAb8VAVQeVfsz=g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Aug 8, 2013 at 2:49 AM, Fujii Masao <fujii(at)postgresql(dot)org> wrote:
> Fix assertion failure by an immediate shutdown.
>
> In PM_WAIT_DEAD_END state, checkpointer process must be dead already.
> But an immediate shutdown could make postmaster's state machine
> transition to PM_WAIT_DEAD_END state even if checkpointer process is
> still running, and which caused assertion failure. This bug was introduced
> in commit 457d6cf049c57cabe9b46ea13f26138040a214ec.

Sorry, this is not true. I copied and pasted wrong commit id. The
right commit id
which introduced this bug is 82233ce7ea42d6ba519aaec63008aff49da6c7af.

Regards,

--
Fujii Masao

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2013-08-08 03:01:09 pgsql: Message style improvements
Previous Message Fujii Masao 2013-08-07 17:49:36 pgsql: Fix assertion failure by an immediate shutdown.