Re: Terminating a backend

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Terminating a backend
Дата
Msg-id 200803101748.m2AHmQT08650@momjian.us
обсуждение исходный текст
Ответ на Terminating a backend  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: Terminating a backend  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Bruce Momjian wrote:
> I have an idea for this TODO item:
> 
>     * Allow administrators to safely terminate individual sessions either
>       via an SQL function or SIGTERM
>     
>       Lock table corruption following SIGTERM of an individual backend
>       has been reported in 8.0.  A possible cause was fixed in 8.1, but
>       it is unknown whether other problems exist.  This item mostly
>       requires additional testing rather than of writing any new code.
>     
>       http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
> 
> When we get the termination signal, why can't we just set a global
> boolean, do a query cancel, and in the setjmp() code block check the
> global and exit --- at that stage we know we have released all locks and
> can exit cleanly.

Should I add this as a TODO?  Seems so.  Tom commented in the patches
queue that it will not work but I don't understand why.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Heikki Linnakangas"
Дата:
Сообщение: Re: [Fwd: Re: [PATCHES] 64-bit CommandIds]
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Terminating a backend