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: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: MauMau <maumau307(at)gmail(dot)com>, 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-30 15:34:53
Message-ID: 20130130153453.GD3355@awork2.anarazel.de (view raw or flat)
Thread:
Lists: pgsql-hackers
On 2013-01-30 10:23:09 -0500, Tom Lane wrote:
> "MauMau" <maumau307(at)gmail(dot)com> writes:
> > When I ran "pg_ctl stop -mi" against the primary, some applications 
> > connected to the primary did not stop. ...
> > The root cause is that gettext() is called in the signal handler quickdie() 
> > via errhint().
> 
> Yeah, it's a known hazard that quickdie() operates like that.

What about not translating those? The messages are static and all memory
needed by postgres should be pre-allocated.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


In response to

Responses

pgsql-hackers by date

Next:From: Jeff JanesDate: 2013-01-30 15:35:46
Subject: Re: autovacuum not prioritising for-wraparound tables
Previous:From: Tom LaneDate: 2013-01-30 15:23:09
Subject: Re: backend hangs at immediate shutdown (Re: Back-branch update releases coming in a couple weeks)

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