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 9B3C1D8C9C for ; Tue, 13 Sep 2005 10:51:42 -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 70101-03 for ; Tue, 13 Sep 2005 13:51:37 +0000 (GMT) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.91]) by svr1.postgresql.org (Postfix) with ESMTP id 52D6DD8C7C for ; Tue, 13 Sep 2005 10:51:38 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 13 Sep 2005 08:51:42 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.4 Date: Tue, 13 Sep 2005 08:51:29 -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/132 X-Sequence-Number: 18869 Thanks, Tom. =20 The statement_timeout setting was also raised on the JDBC list, and has = been checked -- there is nothing setting statement_timeout. The connection= shows this value at zero. None of our code contains anything PostgreSQL = specific, so there is nothing in our framework or applications that would = be aware of the "set statement_timeout" command to be able to issue it. I = created the database instance, the user and the database, and have not set = this as a default anywhere. =20 Regarding the possibility that a ulimit setting is sending the signal, I = am using "su" to set user id to root, issuing the ulimit statements to set = everything unlimited or very high, then using "su" to set user id to = postgres. At that point the settings from root still show. Then I'm = starting postgres using pg_ctl. Is there any reason the ulimit settings = would not carry through with this approach? Is there a better way to do = it? =20 Other than that, what external causes might be at fault when I have both = Windows machines and Linux machines which have nothing installed but the = operating system and PostgreSQL? The only ulimit settings I couldn't set = to "unlimited" were pipe size and open files. Is there any chance that = the error/rollback path in the code is leaking open files on the server? = Is there anything I should run during the test to watch for potential = resource exhaustion? =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