On Fri, Sep 3, 2010 at 11:08 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Fujii Masao <masao.fu...@gmail.com> writes: >>> + * XXX: Is it safe to elog(ERROR) in a signal handler? >>> >>> No, it isn't. > >> We should use elog(FATAL) or check proc_exit_inprogress, instead? > > elog(FATAL) is *certainly* not a better idea. I think there's really > nothing that can be done, you just have to silently ignore the error.
Hmm.. some functions called by a signal handler use elog(FATAL), e.g., RecoveryConflictInterrupt() do that when unknown conflict mode is given as an argument. Are these calls unsafe, too? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
