Skip site navigation (1) Skip section navigation (2)

Re: backend hangs at immediate shutdown (Re: Back-branch update releases coming in a couple weeks)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: MauMau <maumau307(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: backend hangs at immediate shutdown (Re: Back-branch update releases coming in a couple weeks)
Date: 2013-01-31 20:41:21
Message-ID: 510AD6F1.7080804@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On 1/30/13 9:11 AM, MauMau wrote:
> When I ran "pg_ctl stop -mi" against the primary, some applications
> connected to the primary did not stop.  The cause was that the backends
> was deadlocked in quickdie() with some call stack like the following. 
> I'm sorry to have left the stack trace file on the testing machine, so
> I'll show you the precise stack trace tomorrow.

I've had similar problems in the past:

http://www.postgresql.org/message-id/1253704891.20834.8.camel@fsopti579.F-Secure.com

The discussion there never quite concluded.  But yes, you need to be
prepared that in rare circumstances SIGQUIT won't succeed and you need
to use SIGKILL.



In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2013-01-31 20:43:24
Subject: Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used
Previous:From: Christopher BrowneDate: 2013-01-31 20:28:58
Subject: Re: autovacuum not prioritising for-wraparound tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group