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 913AAD885B for ; Tue, 13 Sep 2005 13:31:05 -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 03935-07 for ; Tue, 13 Sep 2005 16:31:03 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B9CF0D6D9D for ; Tue, 13 Sep 2005 13:31:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j8DGV3jL024757; Tue, 13 Sep 2005 12:31:03 -0400 (EDT) To: "Kevin Grittner" Cc: pgsql-admin@postgresql.org Subject: Re: ERROR: canceling query due to user request In-reply-to: References: Comments: In-reply-to "Kevin Grittner" message dated "Tue, 13 Sep 2005 09:51:44 -0500" Date: Tue, 13 Sep 2005 12:31:03 -0400 Message-ID: <24756.1126629063@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/141 X-Sequence-Number: 18878 "Kevin Grittner" writes: > 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? (1) No. (2) Even if we posit the existence of such a serious bug as that, it wouldn't explain how control gets to the SIGINT response code. regards, tom lane