Re: PG-15.6: timeout parameters erroring out

Thanks for your quick responses.

I have just added the session related timeout parameters in the
postgresql.conf file also tried tweaking with different values/patterns
like ('1min', '1 min', 80000, 10s, '10s', '10 s')

but i get an immediate error after reloading the configuration file.

*postgres.log file*
2025-02-10 10:27:10.748 GMT [934108] LOG: received SIGHUP, reloading
configuration files
2025-02-10 10:27:10.749 GMT [934108] LOG: parameter
"idle_in_transaction_session_timeout" changed to "80000"
2025-02-10 10:27:16.117 GMT [2531150] ERROR: trailing junk after numeric
literal at or near "80s" at character 43
2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: SET
idle_in_transaction_session_timeout = 80s

though we are not firing any SQL statements explicitly we see this error.

i guess something else is the issue other than spacing.

Regards
Mukesh Tanuku

On Mon, Feb 10, 2025 at 10:38 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Sunday, February 9, 2025, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com> writes:
>> > We unabled the postgres timeout parameters in the postgresql.conf file
>>
>> > *idle_in_transaction_session_timeout = '1min'idle_session_timeout =
>> '5min'*
>>
> Did you actually run them together on one line like that?
>
>
>>
> I think that is an email client artifact, dealing with RTF or something.
>
> I do agree too much is missing here. The only known errors involve SET
> which configuration file settings don’t use. And those errors are indeed
> the lack of quoting.
>
> The lack of space I mentioned earlier, in the config text literal, is fine.
>
> David J.
>
>