| 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 02:36:57 |
| Message-ID: | 200103120236.VAA28524@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:
> > Not sure. My admin tool is more proof of concept at this point. I
> > think ultimately we will need to allow administrators to such individual
> > backend terminations.
>
> I hope the tool is set up to encourage them to try something safer
> (ie, CANCEL QUERY) first...
Yes, the CANCEL button appears before the TERMINATE button.
On SIGTERM, I think we are fooling ourselves if we think people aren't
SIGTERM'ing individual backends. Terminating individual db connections
is a very common job for an administrator. If SIGTERM doesn't cause
proper shutdown for individual backends, I think it should.
--
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 02:39:08 | Performance monitor renamed |
| Previous Message | Tom Lane | 2001-03-12 02:11:22 | Re: SIGTERM/FATAL error |