One more thought on the topic -- in the particular case where we hit
this, the Statement did not have any requests active on its connection.
If the driver can determine this, it could return from the cancel method
without doing anything.
-Kevin
>>> Oliver Jowett <oliver@opencloud.com> 09/13/05 6:00 PM >>>
Tom Lane wrote:
> This has been discussed before (try the pgsql-jdbc list archives).
> I believe we concluded that an appropriate fix was to not consider the
> cancel request "done" until the client sees the separate connection
> dropped by the postmaster. libpq's cancel functions wait for that to
> happen, and I thought that JDBC had been fixed as well --- maybe you are
> using an old driver version?
I thought this got done too, but looking at the current JDBC driver code
I don't see it..
-O