Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Function to kill backend

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Josh Berkus <josh(at)agliodbs(dot)com>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Function to kill backend
Date: 2004-07-26 01:36:16
Message-ID: 41046010.5030602@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-patches
> The first time I used it was for precisely this reason - some buggy PHP code opened hundreds of connections to a dev server which then remained open doing nothing except wasting resources. It was particularly useful in that case as I didn't have 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, mainly for canceling ather than terminating).

Yeah, I've added the kill and cancel commands to phppgadmin.  I'm happy 
if kill is removed though, i don't want my newbie users panicing their 
machines.

phpmyadmin has both kill and cancel since they're sql commands in mysql.

Chris


In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2004-07-26 01:47:35
Subject: Re: Pipe fixes for win32 services
Previous:From: Bruce MomjianDate: 2004-07-26 01:34:02
Subject: Re: [HACKERS] Function to kill backend

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group