Re: Immediate shutdown causes the assertion failure in 9.4dev

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Immediate shutdown causes the assertion failure in 9.4dev
Date: 2013-08-02 12:21:37
Message-ID: CA+TgmoaWgopaMuBDUAd9f=Fk4h3xqhc5Ur6TfBTwEckSab_0Gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 31, 2013 at 1:26 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Tipton 2013-08-02 12:22:24 Re: Add json_typeof() and json_is_*() functions.
Previous Message Robert Haas 2013-08-02 12:19:10 Re: inconsistent state after crash recovery