>> 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
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
> Those could be pretranslated during startup, but thats mighty ugly.
Are you suggesting to call errmsg_raw() instead of errmsg() in quickdie()?
> 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
If I understand this correctly, I don't think errmsg_raw()
solves the particular problem.
SRA OSS, Inc. Japan
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2013-01-31 01:07:42|
|Subject: Re: pg_dump --pretty-print-views|
|Previous:||From: Tom Lane||Date: 2013-01-31 00:39:58|
|Subject: Re: backend hangs at immediate shutdown|