From: Michael Fuhr <mike@fuhr.org>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: Pgsql-Performance <pgsql-performance@postgresql.org>
Subject: Re: Perl DBD and an alarming problem
Date: Thu, 17 Nov 2005 16:28:57 -0700
Message-ID: <20051117232857.GA49910@winnie.fuhr.org> (raw)
In-Reply-To: <437CF055.6020602@modgraph-usa.com>
References: <BF9F6C0E.13B4A%llonergan@greenplum.com>
<1132136225.5711.4.camel@Panoramix>
<437B9DA9.2030806@modgraph-usa.com>
<20051117002344.GA55377@winnie.fuhr.org>
<437CF055.6020602@modgraph-usa.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, cjames@modgraph-usa.com
Subject: Re: Perl DBD and an alarming problem
In-Reply-To: <20051117232857.GA49910@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox