Re: Log full of: statement_timeout out of the valid range.

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Log full of: statement_timeout out of the valid range.
Date: 2010-01-25 23:33:26
Message-ID: 20100125233326.GA960@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

A. Kretschmer wrote:
> In response to Abraham, Danny :
> > Our setup is a real valid one. Looks like it has to do more with remote
> > connections.
>
> No. 'statement_timeout out of the valid range' has nothing to do with
> remote connections.
>
> >
> > Any idea?
>
> Show us your statement_timeout - setting. If you work with psql, just
> type:
>
> show statement_timeout;
>
> and show us the output.

Obviously, if the value is not valid, it's not getting applied, and thus
it won't show up in SHOW. The '1h' value is valid; it is not the value
causing the log message. The invalid value could come from anywhere.
It could be once per connection or once per query, if Danny is using
some middle layer that injects a "SET statement_timeout TO nnn" for
every query.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2010-01-25 23:44:04 Re: postgres
Previous Message xu fei 2010-01-25 23:30:01 Re: FTS uses "tsquery" directly in the query