| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, sgunderson(at)bigfoot(dot)com |
| Subject: | Re: Kill a session |
| Date: | 2006-07-14 05:50:22 |
| Message-ID: | 8780.1152856222@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Craig A. James" <cjames(at)modgraph-usa(dot)com> writes:
> Bottom line is that I was expecting "instant death" with SIGTERM, but
> instead got an agonizing, drawn out -- but safe -- death of the query.
What was the query exactly?
Our expectation is that all or at least most queries should respond to
SIGINT or SIGTERM interrupts pretty rapidly, say on a less-than-a-second
timescale. However there are various loops in the backend that fail to
execute CHECK_FOR_INTERRUPTS sufficiently often :-(. We've been
gradually finding and fixing these, and will be glad to fix your case
if you provide enough details to pin it down. You might be interested
in this current thread about a similar problem:
http://archives.postgresql.org/pgsql-patches/2006-07/msg00039.php
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Weimer | 2006-07-14 07:05:31 | Re: size of pg_dump files containing bytea values |
| Previous Message | Craig A. James | 2006-07-14 02:23:19 | Re: Kill a session |