> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I am using the SIGTERM in my administration application to allow
> > administrators to kill individual backends. That is why I noticed the
> > message.
>
> Hm. Of course the backend cannot tell the difference between this use
> of SIGTERM and its normal use for system shutdown. Maybe we could
> come up with a compromise message --- although I suspect a compromise
> would just be more confusing.
How about "Connection terminated by administrator", or something like
that.
>
> A more significant issue is whether it's really a good idea to start
> encouraging dbadmins to go around killing individual backends. I think
> this is likely to be a Bad Idea (tm). We have no experience (that I know
> of) with applying SIGTERM for any other purpose than system shutdown or
> forced restart. Are you really prepared to guarantee that shared memory
> will always be left in a consistent state? That there will be no locks
> left locked, etc?
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.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
