| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Terminating a backend |
| Date: | 2008-03-07 01:21:44 |
| Message-ID: | 200803070121.m271Li315581@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
--
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-07 01:34:29 | Re: Terminating a backend |
| Previous Message | Bruce Momjian | 2008-03-07 01:07:07 | Re: Problem identifying constraints which should not be inherited |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-07 01:34:29 | Re: Terminating a backend |
| Previous Message | Tom Lane | 2008-03-07 01:05:02 | Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit |