Re: PG-15.6: timeout parameters erroring out

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PG-15.6: timeout parameters erroring out
Date: 2025-02-10 04:47:20
Message-ID: CAKFQuwZhcbB+HKSW=U-8zBKtjgyi6YfUd6CRVov_z_44OaFCwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday, February 9, 2025, Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com>
wrote:
>
>
>
> *idle_in_transaction_session_timeout = '1min'idle_session_timeout = '5min'*
>

I suspect our docs may need an update. They say you may include white
space before the unit; it probably needs to be changed to “must”. I
believe we’ve recently tightened up the parsing of literals in this area.

>
> other way also, like below
>
> *idle_in_transaction_session_timeout = 60000idle_session_timeout = 300000*
>

If those give error messages regarding trailing junk something else must be
going on.

>
> we see these errors reporting in the logs after we enabled those parameters
> *log:*
> 2025-02-10 04:17:19.156 GMT [2467573] ERROR: trailing junk after numeric
> literal at or near "1m" at character 43
> 2025-02-10 04:17:19.156 GMT [2467573] STATEMENT: SET
> idle_in_transaction_session_timeout = 1min
> 2025-02-10 04:17:19.845 GMT [2467575] ERROR: trailing junk after numeric
> literal at or near "1m" at character 43
> 2025-02-10 04:17:19.845 GMT [2467575] STATEMENT: SET
> idle_in_transaction_session_timeout = 1min
> ...
>

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Rowley 2025-02-10 04:54:06 Re: PG-15.6: timeout parameters erroring out
Previous Message Mukesh Tanuku 2025-02-10 04:34:17 PG-15.6: timeout parameters erroring out