Re: PG-15.6: timeout parameters erroring out

Thanks for clarifying, got it.
Is this issue specifically reported in only the PG 15 version? more syntax
sensitivity.

On Mon, Feb 10, 2025 at 6:09 PM rob stone <floriparob(at)tpg(dot)com(dot)au> wrote:

>
>
> On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:
> > 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.
> >
> >
>
> I'd say that 934108 is the config file reload and that 2531150 is from
> somebody running psql from a shell or SQL code coming out from an
> application.
>
>
>
> >
>