From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SIGTERM/FATAL error |
Date: | 2001-03-12 00:53:15 |
Message-ID: | 200103120053.TAA21006@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > 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.
>
> This is a non-improvement. Please reverse it. SIGTERM would only be
> sent to a backend if the database system were in fact shutting down.
Reversed.
But why say the system is shutting down if the backend is shutting down.
Seems the postmaster should say system shutting down and each backend
should say it is shutting itself down. The way it is now, don't we get
a "system shutting down" message for every running backend?
>
> > Should we be showing the PID's in the server logs more. Do we need to
> > enable that somewhere?
>
> There's already an option for that, but it should not be forced on since
> it will be redundant for those using syslog.
Does syslog show the pid?
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-03-12 00:57:10 | Re: SIGTERM/FATAL error |
Previous Message | Tom Lane | 2001-03-12 00:49:14 | Re: SIGTERM/FATAL error |