Re: [HACKERS] Function to kill backend - Mailing list pgsql-patches

From Dave Page
Subject Re: [HACKERS] Function to kill backend
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E407B39A@ratbert.vale-housing.co.uk
Whole thread Raw
Responses Re: [HACKERS] Function to kill backend  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Re: [HACKERS] Function to kill backend  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches

-----Original Message-----
From: pgsql-patches-owner@postgresql.org on behalf of Magnus Hagander
Sent: Sun 7/25/2004 12:07 PM
To: Tom Lane; Bruce Momjian
Cc: Josh Berkus; PostgreSQL-patches
Subject: Re: [PATCHES] [HACKERS] Function to kill backend

> >much further.  I recall being voted down though ...

> That's not quite the argument I think I had :-) But withuot being able
> to kill the backends, there just no way for me to handle the sitaution
> when I have a hundred clients eating up all available connections and/or
> memory, just sitting idle, because of some freak bug in a client.

The first time I used it was for precisely this reason - some buggy PHP code opened hundreds of connections to a dev
serverwhich then remained open doing nothing except wasting resources. It was particularly useful in that case as I
didn'thave access to the web server at the time. 

Shortly afterwards I added support to pgAdmin's server status tool which has proven quite handy (although I will admit,
mainlyfor canceling ather than terminating). 

I don't know the details of how it works, but is it any worse/better than 'kill -9' (which iirc is no longer considered
anabsolute no-no)? 

Regards, Dave

pgsql-patches by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: [HACKERS] Function to kill backend
Next
From: Andreas Pflug
Date:
Subject: Re: [HACKERS] Function to kill backend