SIGTERM/FATAL error

I have applied the following patch to make SIGTERM backend exit clearer
in the the server logs. "The system" is not really shutting down, but
"the backend" is shutting down.

Should we be showing the PID's in the server logs more. Do we need to
enable that somewhere? Seems they are very hard to follow without
PID's.

---------------------------------------------------------------------------

Index: src/backend/tcop/postgres.c
===================================================================
RCS file: /home/projects/pgsql/cvsroot/pgsql/src/backend/tcop/postgres.c,v
retrieving revision 1.208
diff -c -r1.208 postgres.c
*** src/backend/tcop/postgres.c 2001/02/24 02:04:51 1.208
--- src/backend/tcop/postgres.c 2001/03/11 19:04:47
***************
*** 1022,1028 ****
ProcDiePending = false;
QueryCancelPending = false; /* ProcDie trumps QueryCancel */
ImmediateInterruptOK = false; /* not idle anymore */
! elog(FATAL, "The system is shutting down");
}
if (QueryCancelPending)
{
--- 1022,1028 ----
ProcDiePending = false;
QueryCancelPending = false; /* ProcDie trumps QueryCancel */
ImmediateInterruptOK = false; /* not idle anymore */
! elog(FATAL, "Backend shutting down");
}
if (QueryCancelPending)
{

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026