Re: Immediate shutdown causes the assertion failure in 9.4dev

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Immediate shutdown causes the assertion failure in 9.4dev
Date: 2013-08-02 14:59:05
Message-ID: 20130802145905.GK5669@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas escribió:
> 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?

The one that introduced SIGKILL in immediate-mode stop.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2013-08-02 15:00:45 WIP: Partial match using range key entries
Previous Message Alvaro Herrera 2013-08-02 14:56:58 Re: Add json_typeof() and json_is_*() functions.