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

Re: backend hangs at immediate shutdown

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: andres(at)2ndquadrant(dot)com
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, maumau307(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: backend hangs at immediate shutdown
Date: 2013-01-31 00:40:12
Message-ID: 20130131.094012.1648998302965458635.t-ishii@sraoss.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
>> What about adding a caution to the doc something like:
>> 
>> 	 "pg_ctl -m -i stop" may cause a PostgreSQL hang if native laguage support enabled.
> 
> That doesn't entirely solve the problem, see quote and reply in
> 6845(dot)1359561252(at)sss(dot)pgh(dot)pa(dot)us

Oh, I see now.

> I think adding errmsg_raw() or somesuch that doesn't allocate any memory
> and only accepts constant strings could solve the problem more
> completely, at the obvious price of not allowing translated strings
> directly.
> Those could be pretranslated during startup, but thats mighty ugly.

Are you suggesting to call errmsg_raw() instead of errmsg() in quickdie()?

Tom said:
> That would reduce our exposure slightly, but hardly to zero.  For
> instance, if SIGQUIT happened in the midst of handling a regular error,
> ErrorContext might be pretty full already, necessitating further malloc
> requests.

If I understand this correctly, I don't think errmsg_raw()
solves the particular problem.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp


In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2013-01-31 01:07:42
Subject: Re: pg_dump --pretty-print-views
Previous:From: Tom LaneDate: 2013-01-31 00:39:58
Subject: Re: backend hangs at immediate shutdown

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