Re: Cancel/Kill backend functions

Arrgh, when will I ever learn :-(

Attached.

//Magnus


>-----Original Message-----
>From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
>Sent: den 26 maj 2004 20:50
>To: Magnus Hagander
>Cc: Neil Conway; pgsql-patches@postgresql.org
>Subject: Re: [PATCHES] Cancel/Kill backend functions
>
>
>
>Magnus, would you please resumbit this as a context diff?
>
>---------------------------------------------------------------
>------------
>
>Magnus Hagander wrote:
>> Okay, here is an updated patch. now uses IsBackendPid(), which is
>> closely modeled (read cut-and-pasted) from
>> TransactionIdIsInProgress().
>>
>> Since it's no longer a pgstat function, I moved it to "misc.c". Not
>> 100% that's the right place either, but it seemed like the best
>> alternative.
>>
>> //Magnus
>>
>>
>> >-----Original Message-----
>> >From: Neil Conway [mailto:neilc@samurai.com]
>> >Sent: den 22 maj 2004 10:00
>> >To: Magnus Hagander
>> >Cc: pgsql-patches@postgresql.org
>> >Subject: Re: [PATCHES] Cancel/Kill backend functions
>> >
>> >
>> >Magnus Hagander wrote:
>> >> Per previous discussions, here are two functions to send INT and
>> >> TERM signals to other backends.They permit only INT and TERM, and
>> >> permits sending only to postgresql backends (as registered in
>> >> pgstat).
>> >
>> >Why does this depend on pgstat? ISTM it would be better to use the
>> >per-backend PGPROC information, which is stored in shared memory.
>> >Consider TransactionIdIsInProgress() for an example.
>> >
>> >-Neil
>> >
>
>Content-Description: termbackend.patch
>
>[ Attachment, skipping... ]
>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 7: don't forget to increase your free space map settings
>
>--
>  Bruce Momjian                        |  http://candle.pha.pa.us
>  pgman@candle.pha.pa.us               |  (610) 359-1001
>  +  If your life is a hard drive,     |  13 Roberts Road
>  +  Christ can be your backup.        |  Newtown Square,
>Pennsylvania 19073
>