Re: [HACKERS] Function to kill backend

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Magnus Hagander" <mha(at)sollentuna(dot)net>, "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 07:58:27
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A7436@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 26 July 2004 04:46
> To: Dave Page
> Cc: Magnus Hagander; Bruce Momjian; Josh Berkus; PostgreSQL-patches
> Subject: Re: [PATCHES] [HACKERS] Function to kill backend
>
> If you don't mind plastering a "use at your own risk" sign on
> it, then go for it.

Nah, I'll follow your lead on this one - if you don't think it's safe
(and it absolutely must be of course), who am I to argue?

:-)

Regards, Dave.

Browse pgsql-patches by date

  From Date Subject
Next Message Oliver Jowett 2004-07-26 11:42:25 fix for parameterized queries in DECLARE CURSOR statements
Previous Message Tom Lane 2004-07-26 05:16:00 Re: pgxs: build infrastructure for extensions v4