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

From Alvaro Herrera
Subject Re: Immediate shutdown causes the assertion failure in 9.4dev
Date
Msg-id 20130802145905.GK5669@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Immediate shutdown causes the assertion failure in 9.4dev  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas escribió:
> 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?

The one that introduced SIGKILL in immediate-mode stop.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add json_typeof() and json_is_*() functions.
Next
From: Antonin Houska
Date:
Subject: WIP: Partial match using range key entries