| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | andrew(at)supernews(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_terminate_backend idea |
| Date: | 2005-06-22 18:39:28 |
| Message-ID: | 20115.1119465568@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew - Supernews <andrew+nonews(at)supernews(dot)com> writes:
> On 2005-06-22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>>> I've seen cancel *not* working.
>>
>> Even a moment's perusal of the code will prove that there is no
>> situation in which a backend will respond to SIGTERM but not SIGINT
> "idle in transaction". (or "idle" for that matter, but that's usually less
> significant.)
In that case there's no query to cancel, so I would dispute the claim
that that constitutes "not working". QueryCancel is defined to cancel
the current query, not necessarily to abort your whole transaction.
(Before 8.0 there wasn't much of a difference, but now there is:
QueryCancel is an ordinary error that can be trapped by a savepoint.
Are you arguing it should not be so trappable?)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-06-22 19:25:00 | Re: [PATCHES] O_DIRECT for WAL writes |
| Previous Message | Andrew - Supernews | 2005-06-22 18:16:36 | Re: pg_terminate_backend idea |