From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Terminating a backend |
Date: | 2008-03-10 17:48:26 |
Message-ID: | 200803101748.m2AHmQT08650@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-10 17:57:45 | Re: Terminating a backend |
Previous Message | Andrew Dunstan | 2008-03-10 17:38:33 | Re: CopyReadLineText optimization |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-10 17:57:45 | Re: Terminating a backend |
Previous Message | Andrew Dunstan | 2008-03-10 17:38:33 | Re: CopyReadLineText optimization |