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

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: (view raw, whole thread or download thread mbox)
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.


>-----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.

Attachment: termbackend.patch
Description: application/octet-stream (3.3 KB)


pgsql-patches by date

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

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