X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E85FAD71A8 for ; Thu, 17 Nov 2005 19:29:01 -0400 (AST) 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 82521-04 for ; Thu, 17 Nov 2005 23:29:03 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 2B943DB98D for ; Thu, 17 Nov 2005 19:28:58 -0400 (AST) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id jAHNSwZX049688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 16:29:00 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id jAHNSvR4050568; Thu, 17 Nov 2005 16:28:57 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id jAHNSvdR050567; Thu, 17 Nov 2005 16:28:57 -0700 (MST) (envelope-from mfuhr) Date: Thu, 17 Nov 2005 16:28:57 -0700 From: Michael Fuhr To: "Craig A. James" Cc: Pgsql-Performance Subject: Re: Perl DBD and an alarming problem Message-ID: <20051117232857.GA49910@winnie.fuhr.org> References: <1132136225.5711.4.camel@Panoramix> <437B9DA9.2030806@modgraph-usa.com> <20051117002344.GA55377@winnie.fuhr.org> <437CF055.6020602@modgraph-usa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <437CF055.6020602@modgraph-usa.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/337 X-Sequence-Number: 15594 On Thu, Nov 17, 2005 at 01:04:21PM -0800, Craig A. James wrote: > When I set statement_timeout in the config file, it just didn't do anything > - it never timed out (PG 8.0.3). I finally found in the documentation that > I can do "set statement_timeout = xxx" from PerlDBI on a per-client basis, > and that works. You probably shouldn't set statement_timeout on a global basis anyway, but did you reload the server after you made the change? Setting statement_timeout in postgresql.conf and then reloading the server works here in 8.0.4. -- Michael Fuhr