1
0
mirror of https://github.com/postgres/postgres.git synced 2025-10-19 15:49:24 +03:00

Modify elog() logic so that it won't try to longjmp(Warn_restart) before

Warn_restart has been set by the backend main loop.  This means that
elog(ERROR) or elog(FATAL) in the postmaster or during backend startup
now have well-defined behavior: proc_exit() rather than coredump.
In the case of elog() inside the postmaster, I think that proc_exit()
is probably not enough --- don't we want our child backends to be
forced to quit too?  But I don't understand Vadim's recent changes in
this area, so I'll leave it to him to look over and tweak if needed.
This commit is contained in:
Tom Lane
1999-11-16 06:13:36 +00:00
parent dc5c7713bc
commit e1492cc34c
3 changed files with 22 additions and 14 deletions

View File

@@ -6,7 +6,7 @@
*
* Copyright (c) 1994, Regents of the University of California
*
* $Id: tcopprot.h,v 1.22 1999/10/06 21:58:18 vadim Exp $
* $Id: tcopprot.h,v 1.23 1999/11/16 06:13:34 tgl Exp $
*
* OLD COMMENTS
* This file was created so that other c files could get the two
@@ -37,6 +37,7 @@
#define siglongjmp longjmp
#endif
extern DLLIMPORT sigjmp_buf Warn_restart;
extern bool Warn_restart_ready;
extern bool InError;
extern bool ExitAfterAbort;