From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mukesh Tanuku <mukesh.postgres@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: PG-15.6: timeout parameters erroring out
In-reply-to: <CAJzgB-Fjr0VkswdA=zytN1PXU4=hMFaK0RoR9MX4x+FNc6QCWw@mail.gmail.com>
References: <CAJzgB-Fjr0VkswdA=zytN1PXU4=hMFaK0RoR9MX4x+FNc6QCWw@mail.gmail.com>
Comments: In-reply-to Mukesh Tanuku <mukesh.postgres@gmail.com>
	message dated "Mon, 10 Feb 2025 10:04:17 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2106556.1739163733.1@sss.pgh.pa.us>
Date: Mon, 10 Feb 2025 00:02:13 -0500
Message-ID: <2106557.1739163733@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2106557.1739163733%40sss.pgh.pa.us>
Precedence: bulk

Mukesh Tanuku <mukesh.postgres@gmail.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?  The normal
thing is one setting per line.  It might be that the config file
parser will let you get away with just spaces rather than a newline
between settings, but I'm not terribly surprised if it fails without
any whitespace at all.  However, since you showed us neither the exact
config file contents nor the error message you got, this is all just
speculation.

> 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

This case however is pretty clear: you need single quotes around the
value '1min', and you didn't provide them.

			regards, tom lane