Re: Cancel/Kill backend functions - Mailing list pgsql-patches

From Magnus Hagander
Subject Re: Cancel/Kill backend functions
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE34BAC3@algol.sollentuna.se
Whole thread Raw
In response to Cancel/Kill backend functions  ("Magnus Hagander" <mha@sollentuna.net>)
Responses Re: Cancel/Kill backend functions
List pgsql-patches
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
>

Attachment

pgsql-patches by date:

Previous
From: ssinger@navtechinc.com
Date:
Subject: contrib/dbmirror typo fix
Next
From: "Magnus Hagander"
Date:
Subject: Small patch for oracle_compat.c