Skip site navigation (1) Skip section navigation (2)

Re: Statement.cancel() race condition

From: Kris Jurka <books(at)ejurka(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Statement.cancel() race condition
Date: 2005-12-01 23:39:15
Message-ID: Pine.BSO.4.61.0512011833110.24595@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Thu, 1 Dec 2005, Kevin Grittner wrote:

>
> The problem is that even after the exception comes out of this code, is
> caught, and the transaction is rolled back -- we are still often able to
> start another statement which is running by the time the server gets
> around to interrupting the related back end process.  Obviously, having
> the cancel of one statement actually interrupt the processing of a
> subsequent statement violates the popular principle of "least surprising
> result".
>

I think taking the ReceiveEOF portion of this patch:

http://archives.postgresql.org/pgsql-jdbc/2003-09/msg00175.php

would fix this in the single thread case.  The multi-threaded case is 
obviously more complicated.  I don't recall why the original patch wasn't 
committed.

Kris Jurka

In response to

Responses

pgsql-jdbc by date

Next:From: Kris JurkaDate: 2005-12-02 03:13:53
Subject: Re: Statement.cancel() race condition
Previous:From: Kevin GrittnerDate: 2005-12-01 23:07:45
Subject: Statement.cancel() race condition

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group