X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 89168D8F01; Thu, 15 Sep 2005 11:23:14 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37564-05; Thu, 15 Sep 2005 14:23:10 +0000 (GMT) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.91]) by svr1.postgresql.org (Postfix) with ESMTP id 70D84D8E0E; Thu, 15 Sep 2005 11:23:11 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Thu, 15 Sep 2005 09:23:16 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Thu, 15 Sep 2005 09:22:58 -0500 From: "Kevin Grittner" To: , Cc: , Subject: Re: [JDBC] ERROR: canceling query due to user request Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 required=5 tests=[AWL=0.004] X-Spam-Level: X-Archive-Number: 200509/174 X-Sequence-Number: 18911 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. =20 -Kevin =20 =20 >>> Oliver Jowett 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