Обсуждение: Log full of: statement_timeout out of the valid range.
Our setup is a real valid one. Looks like it has to do more with remote connections.
Any idea?
Thanks
Danny
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. Andreas -- Andreas Kretschmer Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header) GnuPG: 0x31720C99, 1006 CCB4 A326 1D42 6431 2EB0 389D 1DC2 3172 0C99
On Mon, 2010-01-25 at 09:09 -0600, Abraham, Danny wrote: > Our setup is a real valid one. Looks like it has to do more with > remote connections. > A remote connection trying to set statement_timeout on its own and sending an invalid value. Joshua D. Drake > Any idea? > > Thanks > > Danny > > > > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.
ctrlm700=> show statement_timeout;
statement_timeout
-------------------
1h
(1 row)
Abraham, Danny <danny_abraham@bmc.com> wrote: > ctrlm700=> show statement_timeout; > > statement_timeout > > ------------------- > > 1h I'm not sure if this is a valid value, the documentation says: statement_timeout (integer) Abort any statement that takes over the specified number of milliseconds If you really want 1 hour try to change that to 3600000. But maybe i'm wrong and you should read the other answer from Joshua Drake. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
On Mon, 2010-01-25 at 09:09 -0600, Abraham, Danny wrote: > Our setup is a real valid one. Looks like it has to do more with > remote connections. > A remote connection trying to set statement_timeout on its own and sending an invalid value. Joshua D. Drake > Any idea? > > Thanks > > Danny > > > > -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.
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.
On 26/01/2010 12:31 AM, Joshua D. Drake wrote: > On Mon, 2010-01-25 at 09:09 -0600, Abraham, Danny wrote: >> Our setup is a real valid one. Looks like it has to do more with >> remote connections. >> > > A remote connection trying to set statement_timeout on its own and > sending an invalid value. > > Joshua D. Drake > > >> Any idea? To find out what's doing it and what it's trying to set, turn on statement logging. -- Craig Ringer