Re: Cancel/Kill backend functions

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Neil Conway" <neilc(at)samurai(dot)com>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Cancel/Kill backend functions
Date: 2004-05-24 19:27:30
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34BAC3@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)samurai(dot)com]
>Sent: den 22 maj 2004 10:00
>To: Magnus Hagander
>Cc: pgsql-patches(at)postgresql(dot)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 Content-Type Size
termbackend.patch application/octet-stream 3.3 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2004-05-24 21:57:12 Small patch for oracle_compat.c
Previous Message ssinger 2004-05-24 16:32:21 contrib/dbmirror typo fix