From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SIGTERM/FATAL error |
Date: | 2001-03-12 01:33:06 |
Message-ID: | 3AAC2752.4F82ED96@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> 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.
>
> > 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?
>
> You are failing to consider that the primary audience for this error
> message is not the system log, but the clients of the backends. They
> are going to see only one message, and they are going to want to know
> *why* their backend shut down.
>
How could the backend know why it is shut down ?
Is it inhibited to kill a backend individually ?
What is a real syetem shut down message ?
I agree with Bruce to change the backend shut down
message.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-12 01:54:56 | Re: SIGTERM/FATAL error |
Previous Message | Bruce Momjian | 2001-03-12 01:11:59 | Re: SIGTERM/FATAL error |