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 3F6B6D8C83 for ; Mon, 12 Sep 2005 19:39:46 -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 36372-02 for ; Mon, 12 Sep 2005 22:39:41 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6EE60D8C7D for ; Mon, 12 Sep 2005 19:39:41 -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 j8CMdiok006249; Mon, 12 Sep 2005 18:39:44 -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 "Mon, 12 Sep 2005 15:54:43 -0500" Date: Mon, 12 Sep 2005 18:39:44 -0400 Message-ID: <6248.1126564784@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/114 X-Sequence-Number: 18851 "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