X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A89628B9C27 for ; Thu, 3 Feb 2005 06:49:55 +0000 (GMT) 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 93555-06 for ; Thu, 3 Feb 2005 06:49:44 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 5032A8B9B9A for ; Thu, 3 Feb 2005 06:49:44 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j136nL0M010593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Feb 2005 23:49:23 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j136nLQT047078; Wed, 2 Feb 2005 23:49:21 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j136nLBV047077; Wed, 2 Feb 2005 23:49:21 -0700 (MST) (envelope-from mfuhr) Date: Wed, 2 Feb 2005 23:49:20 -0700 From: Michael Fuhr To: Luiz Rafael Culik Guimaraes Cc: pgsql-sql@postgresql.org Subject: Re: problem with postgres Message-ID: <20050203064920.GA47031@winnie.fuhr.org> References: <1101136693.18148.66.camel@richard> <1101149501.18148.81.camel@richard> <002d01c50990$4f187270$0105a8c0@Luizrafael> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <002d01c50990$4f187270$0105a8c0@Luizrafael> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/56 X-Sequence-Number: 20167 On Wed, Feb 02, 2005 at 11:33:03PM -0200, Luiz Rafael Culik Guimaraes wrote: > i´m getting many message of > Erro:canceling query due to user request What does the following query show? SHOW statement_timeout; If statement_timeout isn't 0 (zero) and if you didn't change it in postgresql.conf, then maybe you're picking it up from a per-user or per-database configuration. You can check such settings with the following queries: SELECT usename, useconfig FROM pg_user; SELECT datname, datconfig FROM pg_database; You can use ALTER USER or ALTER DATABASE to change the settings. -- Michael Fuhr http://www.fuhr.org/~mfuhr/