Re: Cancel/Kill backend functions
| От | Magnus Hagander | 
|---|---|
| Тема | Re: Cancel/Kill backend functions | 
| Дата | |
| Msg-id | 6BCB9D8A16AC4241919521715F4D8BCE34BAC3@algol.sollentuna.se обсуждение исходный текст | 
| Ответ на | Cancel/Kill backend functions ("Magnus Hagander" <mha@sollentuna.net>) | 
| Ответы | Re: Cancel/Kill backend functions | 
| Список | 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 >
Вложения
В списке pgsql-patches по дате отправления: