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 B7D10D8D24 for ; Tue, 13 Sep 2005 11:51:55 -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 83129-07 for ; Tue, 13 Sep 2005 14:51:48 +0000 (GMT) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.91]) by svr1.postgresql.org (Postfix) with ESMTP id 3ECC5D8D19 for ; Tue, 13 Sep 2005 11:51:49 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 13 Sep 2005 09:51:54 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Tue, 13 Sep 2005 09:51:44 -0500 From: "Kevin Grittner" To: Cc: Subject: Re: 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.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200509/134 X-Sequence-Number: 18871 One more thought -- I keep coming back to the fact that when we turn on = logging in the JDBC driver on the client side, the problem does not occur. = The only possible reason I can see for this having any affect on the = problem is the small delay introduced by the synchronous logging. Since = this is only showing up on commit of a database transaction which follows = close on the heels of a rollback on the same connection, is there any = chance that there is some very small "settling time" needed for a = rollback, and we're sometimes getting in ahead of this? =20 -Kevin =20 =20 >>> Tom Lane 09/12/05 5:39 PM >>> "Kevin Grittner" writes: > org.postgresql.util.PSQLException: ERROR: canceling query due to user = request The only possible trigger of that message is a SIGINT sent to the backend. Now the backend will SIGINT itself if a statement timeout expires, so one possibility is that you have statement_timeout set and it's getting exceeded. Otherwise you need to be looking for external causes. regards, tom lane