MIME-Version: 1.0
References: <CAJzgB-Fjr0VkswdA=zytN1PXU4=hMFaK0RoR9MX4x+FNc6QCWw@mail.gmail.com>
 <2106557.1739163733@sss.pgh.pa.us> <CAKFQuwY6VqAAHxHK73oymxwg=nRpEnTnQQNBq+fTtjR+Fecp=A@mail.gmail.com>
 <CAJzgB-FjAsqANqVM8gxdo1aYqeZVvoHrW25c84y2711aca47Sg@mail.gmail.com> <788aca1329878b3fbc93da929bd54b758ec5e4b4.camel@tpg.com.au>
In-Reply-To: <788aca1329878b3fbc93da929bd54b758ec5e4b4.camel@tpg.com.au>
From: Mukesh Tanuku <mukesh.postgres@gmail.com>
Date: Mon, 10 Feb 2025 19:04:12 +0530
Message-ID: <CAJzgB-Fr+_4tEgHd9FPO_KbvnVSEMMiBjQxJ3TaJugS=hUgZCg@mail.gmail.com>
Subject: Re: PG-15.6: timeout parameters erroring out
To: rob stone <floriparob@tpg.com.au>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000403ee8062dc9c47f"
Archived-At: <https://www.postgresql.org/message-id/CAJzgB-Fr%2B_4tEgHd9FPO_KbvnVSEMMiBjQxJ3TaJugS%3DhUgZCg%40mail.gmail.com>
Precedence: bulk

--000000000000403ee8062dc9c47f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM rob stone <floriparob@tpg.com.au> w=
rote:

>
>
> 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 =3D 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.
>
>
>
> >
>

--000000000000403ee8062dc9c47f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks for clarifying, got it.=C2=A0<div>Is this issue spe=
cifically reported in only the PG 15 version? more syntax sensitivity.=C2=
=A0</div></div><br><div class=3D"gmail_quote gmail_quote_container"><div di=
r=3D"ltr" class=3D"gmail_attr">On Mon, Feb 10, 2025 at 6:09=E2=80=AFPM rob =
stone &lt;<a href=3D"mailto:floriparob@tpg.com.au">floriparob@tpg.com.au</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br=
>
<br>
On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote:<br>
&gt; Thanks for your quick=C2=A0responses.<br>
&gt; <br>
&gt; I have just added the session related timeout parameters in the<br>
&gt; postgresql.conf file also tried tweaking with different<br>
&gt; values/patterns like (&#39;1min&#39;, &#39;1 min&#39;, 80000, 10s, =
9;10s&#39;, &#39;10 s&#39;)<br>
&gt; <br>
&gt; but i get an immediate error after reloading the configuration file.=
=C2=A0<br>
&gt; <br>
&gt; postgres.log file<br>
&gt; 2025-02-10 10:27:10.748 GMT [934108] LOG: =C2=A0received SIGHUP, reloa=
ding<br>
&gt; configuration files<br>
&gt; 2025-02-10 10:27:10.749 GMT [934108] LOG: =C2=A0parameter<br>
&gt; &quot;idle_in_transaction_session_timeout&quot; changed to &quot;80000=
&quot;<br>
&gt; 2025-02-10 10:27:16.117 GMT [2531150] ERROR: =C2=A0trailing junk after=
<br>
&gt; numeric literal at or near &quot;80s&quot; at character 43<br>
&gt; 2025-02-10 10:27:16.117 GMT [2531150] STATEMENT: =C2=A0SET<br>
&gt; idle_in_transaction_session_timeout =3D 80s<br>
&gt; <br>
&gt; though we are not firing any SQL statements explicitly=C2=A0we see thi=
s<br>
&gt; error.<br>
&gt; <br>
&gt; i guess something else is the issue other than spacing.<br>
&gt; <br>
&gt; <br>
<br>
I&#39;d say that 934108 is the config file reload and that 2531150 is from<=
br>
somebody running psql from a shell or SQL code coming out from an<br>
application.<br>
<br>
<br>
<br>
&gt; <br>
</blockquote></div>

--000000000000403ee8062dc9c47f--