From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Cc: sgunderson@bigfoot.com
Subject: Re: Kill a session
Date: Fri, 14 Jul 2006 01:50:22 -0400
Message-ID: <8780.1152856222@sss.pgh.pa.us> (raw)
In-Reply-To: <44B70017.6000703@modgraph-usa.com>
References: <6BCB9D8A16AC4241919521715F4D8BCEA0FAE8@algol.sollentuna.se>
<44B51896.1000808@modgraph-usa.com>
<20060712170404.GA27392@uio.no>
<44B70017.6000703@modgraph-usa.com>
"Craig A. James" <cjames@modgraph-usa.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, cjames@modgraph-usa.com, sgunderson@bigfoot.com
Subject: Re: Kill a session
In-Reply-To: <8780.1152856222@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox