Re: Perl DBD and an alarming problem

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com>
Cc: Pgsql-Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Perl DBD and an alarming problem
Date: 2005-11-17 23:28:57
Message-ID: 20051117232857.GA49910@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Guillaume Smet 2005-11-17 23:35:06 Re: weird performances problem
Previous Message Andrew Sullivan 2005-11-17 22:13:14 Re: weird performances problem