Paul Thomas <paul@tmsl.demon.co.uk> writes:
> On 09/09/2004 10:41 Oliver Jowett wrote:
>> JDBC gives you no way to ensure you only call cancel() on a running query
>> (there's a race between query execution returning and the call to
>> cancel()). Calling cancel() on a statement that's not currently executing
>> should do nothing; if it ends up cancelling a future query, it's a driver
>> bug.
> Thanks for the explaination Oliver. Maybe there is a driver bug then?
IIRC there was such a bug at one time, but I thought it had been fixed.
Maybe the problem is use of an old driver?
regards, tom lane