Re: Immediate shutdown causes the assertion failure in 9.4dev - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Immediate shutdown causes the assertion failure in 9.4dev
Date
Msg-id CA+TgmoaWgopaMuBDUAd9f=Fk4h3xqhc5Ur6TfBTwEckSab_0Gg@mail.gmail.com
Whole thread Raw
In response to Immediate shutdown causes the assertion failure in 9.4dev  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Immediate shutdown causes the assertion failure in 9.4dev  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jul 31, 2013 at 1:26 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
> I encountered the following assertion failure when I executed
> an immediate shutdown.
>
> LOG:  received immediate shutdown request
> WARNING:  terminating connection because of crash of another server process
> DETAIL:  The postmaster has commanded this server process to roll back
> the current transaction and exit, because another server process
> exited abnormally and possibly corrupted shared memory.
> HINT:  In a moment you should be able to reconnect to the database and
> repeat your command.
> TRAP: FailedAssertion("!(CheckpointerPID == 0)", File: "postmaster.c",
> Line: 3440)
>
> The cause of this problem seems to be that PostmasterStateMachine()
> may fail to wait for the checkpointer to exit. Attached patch fixes this.

What commit broke this?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: inconsistent state after crash recovery
Next
From: Andrew Tipton
Date:
Subject: Re: Add json_typeof() and json_is_*() functions.