| 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:57:10 |
| Message-ID: | 200103120057.TAA21891@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.
Also, what signal should people send to a backend to kill just that
backend? In my reading of the code, I see:
pqsignal(SIGTERM, die); /* cancel current query and exit */
pqsignal(SIGQUIT, die); /* could reassign this sig for another use */
Are either of them safe?
--
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 | Tom Lane | 2001-03-12 01:06:31 | Re: SIGTERM/FATAL error |
| Previous Message | Bruce Momjian | 2001-03-12 00:53:15 | Re: SIGTERM/FATAL error |