Re: Statement.cancel() may cancel queries in the future

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Statement.cancel() may cancel queries in the future
Date: 2003-09-15 22:17:36
Message-ID: 3425.1063664256@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Oliver Jowett <oliver(at)opencloud(dot)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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Yang Soon Chiao 2003-09-16 01:12:10 Re: cannot start tomcat
Previous Message Oliver Jowett 2003-09-15 22:07:45 Re: Statement.cancel() may cancel queries in the future