Re: Statement.cancel() may cancel queries in the future - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: Statement.cancel() may cancel queries in the future
Date
Msg-id 3425.1063664256@sss.pgh.pa.us
Whole thread Raw
In response to Re: Statement.cancel() may cancel queries in the future  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: Statement.cancel() may cancel queries in the future  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-jdbc
Oliver Jowett <oliver@opencloud.com> writes:
> On Mon, Sep 15, 2003 at 12:01:47PM -0400, Tom Lane wrote:
>> You could make things a lot closer to
>> synchronous if you wait for the postmaster to drop the connection,
>> instead.  That would guarantee that the postmaster has completed
>> executing kill().  I suppose actual delivery of the signal to the
>> backend might not have happened yet, but it's hard to believe that
>> it could be postponed past the backend's next successful execution of
>> recv().

> That sounds reasonable. I'll put together a patch to do that.

It looks like libpq has the same issue, as PQrequestCancel() does not
wait around for the postmaster to drop the connection.  Anyone want
to fix that?

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Statement.cancel() may cancel queries in the future
Next
From: "Yang Soon Chiao"
Date:
Subject: Re: cannot start tomcat