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: | Magnus Hagander <mha(at)sollentuna(dot)net>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Function to kill backend |
Date: | 2004-04-06 15:41:28 |
Message-ID: | 200404061541.i36FfSq19739@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> > But are you saying it *is* safe with SIGTERM to a backend?
>
> I'm saying I'm not happy about promoting that to the status of a
> supported feature. Up to now it's always been "if it breaks you
> get to keep both pieces", but if there's a built-in function to do it
> then people will naturally expect a certain level of reliability.
>
> Maybe it works fine, maybe it doesn't. But I foresee having to expend
> work down the road because of this addition.
I assume admins are already doing this (via kill), so whether it is
supported or not, we should give folks a safe way to do this. This
seems like basic functionality we should be giving admins, even if it
does take some work on our part.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-06 15:48:25 | Re: Function to kill backend |
Previous Message | Bruce Momjian | 2004-04-06 15:38:53 | Re: [HACKERS] logging statement levels |