Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thRAn-002PzN-NM for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 10:37:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1thR9o-000HS6-A8 for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 10:36:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thR9n-000HRx-Ti for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 10:36:51 +0000 Received: from mail-yw1-x1135.google.com ([2607:f8b0:4864:20::1135]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thR9k-0000VL-32 for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 10:36:51 +0000 Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-6fb0200b193so3585037b3.0 for ; Mon, 10 Feb 2025 02:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739183807; x=1739788607; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=E7ehendEdemqUI23Czp4Q3R90Tnu2DJU7Uxo6KuJTbI=; b=Z9XTUhgjqpjrDfRdPssqiKfoP/rXxO3ehaJcCfVgSjx4P9eo06v7PxOYM7Jlh8OGGh Behej+vZxNdVlF5tZQHRBUbOphISki32L6Its2/niExNlG/To5BYfnlqaMp7mO6ZUggA td6ZfE5QvLay0k2juOCQ/b+21o0a1vgFhwvY2havGB9sfpDgM/Ch15loQkdpjVO8AEPW PNmzkC/lrWyiVoXcwUZ2Azv+s81rWEdEiIKuLvJYkEmUFdW30lsGMqr7ey6xZqnszVcA jKrqVu7a8RrCAW7sikD8D3ujzJ5DPXn+29XIPRCPljiZWoqoBaKjyq4AhzTTxrBc5YlN aCPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739183807; x=1739788607; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=E7ehendEdemqUI23Czp4Q3R90Tnu2DJU7Uxo6KuJTbI=; b=L0UeqYL72DWSIAdEP9V/nRgCqeqD3LcztKGZEuSLwmJNcz2t9qPSGPWPKi1hq3MVt0 8i1G3eb37g4wWosA3Ld0V4/bbpDIpsnyY87JLzXxd1N7uSbDU+10qAVtD+jRoBZhUe/+ t5AMhszD3FPaBFqDvpHuiBndMKORbptPxiwrHBvE2/1n7Im/n07nGEC3SC8jIDiChYBi oysUd2rnURK9Yk3yKOcThq11v/5HADPArL+z9ZlYeTIw83ueeYPjCbtmIX1pxo1s8FGq EKY4v1F8b6QNqISXl+eCj4F030/TEJGYEpuyjU6kIhjJJS0LifreOEPNAj3zbvpQJC8m pPqg== X-Forwarded-Encrypted: i=1; AJvYcCWjm42TW6Ehy01N0E+kG/KKd/YWTo+nU2Uh2w0c59TiWhJCzAo0XPFcQ8eFiBNyWjhqBOYBkgwKD1VHH092@lists.postgresql.org X-Gm-Message-State: AOJu0YxDUcpr2JLflwOBDguzotIqcLKk21WmK5yJaTHOy7B4/xz+Lobf ZAgonlKMkyCyEowMtOONkPLj1TG24YxrfQy2qInu1wKPTCAE5+eHIj8E8T1rflhAxuv6WX7Q9S2 Hr2QNQkI0P+uPABx+b0aRW0ym+Bg= X-Gm-Gg: ASbGncvcBGmaOEocap8L6X6DA9+6iFhoo3A4jF3NSfkny0HpbGL+bTenWoZ47hlTrq/ mCf9krhAIbLMLvvUt7yYqAB2bgZa5ylrVKJWhawKTErzRn4UVUL61yaZIcHFckGyfrKE+tWiM6g == X-Google-Smtp-Source: AGHT+IFyHNFmZHgeUw2CG/VyHBvXifqrxxiPQof+8WIAMKkYszBLd9aVSI6xWG+CgwdVIIpvL0C0lt2BFCjVzVCEbpg= X-Received: by 2002:a05:690c:628a:b0:6f7:598d:34c2 with SMTP id 00721157ae682-6f9b29e3d10mr101215137b3.24.1739183807541; Mon, 10 Feb 2025 02:36:47 -0800 (PST) MIME-Version: 1.0 References: <2106557.1739163733@sss.pgh.pa.us> In-Reply-To: From: Mukesh Tanuku Date: Mon, 10 Feb 2025 16:06:36 +0530 X-Gm-Features: AWEUYZla1pDKIKZ3_WrulAeJgH7fVywpydkhGogvoCqa9r1N4x90fYi0rpvG14k Message-ID: Subject: Re: PG-15.6: timeout parameters erroring out To: "David G. Johnston" Cc: Tom Lane , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000000c370b062dc74920" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000c370b062dc74920 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. Regards Mukesh Tanuku On Mon, Feb 10, 2025 at 10:38=E2=80=AFAM David G. Johnston < david.g.johnston@gmail.com> wrote: > On Sunday, February 9, 2025, Tom Lane wrote: > >> Mukesh Tanuku writes: >> > We unabled the postgres timeout parameters in the postgresql.conf file >> >> > *idle_in_transaction_session_timeout =3D '1min'idle_session_timeout = =3D >> '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=E2=80=99t use. And those errors ar= e indeed > the lack of quoting. > > The lack of space I mentioned earlier, in the config text literal, is fin= e. > > David J. > > --0000000000000c370b062dc74920 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for your quick=C2=A0responses.

I= have just added the session related timeout parameters in the postgresql.c= onf 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 configura= tion file.=C2=A0

postgres.log file2025-02-10 10:27:10.748 GMT [934108] LOG: =C2=A0received SIGHUP, reloadin= g configuration files
2025-02-10 10:27:10.749 GMT [934108] LOG: =C2=A0pa= rameter "idle_in_transaction_session_timeout" changed to "80= 000"
2025-02-10 10:27:16.117 GMT [2531150] ERROR: =C2=A0trailing ju= nk after numeric literal at or near "80s" at character 43
2025= -02-10 10:27:16.117 GMT [2531150] STATEMENT: =C2=A0SET idle_in_transaction_= session_timeout =3D 80s

though we are not firi= ng any SQL statements explicitly=C2=A0we see this error.

i guess something else is the issue other than spacing.
Regards
Mukesh Tanuku


=
On Mon, Feb 10, 2025 at 10:38=E2=80=AFAM David G. Johnston <= david.g.johnston@gmail.com> wrote:
On = Sunday, February 9, 2025, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Mukesh Tanuku <mukesh.postgres@gmail.com> write= s:
> We unabled the postgres timeout parameters in the postgresql.conf file=

> *idle_in_transaction_session_timeout =3D '1min'idle_session_ti= meout =3D '5min'*=C2=A0
Did you actually run them together on one line like that?


I think that is an email client artifact, dealing with RTF or someth= ing.

I do agree too much is missing here.=C2=A0 Th= e only known errors involve SET which configuration file settings don=E2=80= =99t use.=C2=A0 And those errors are indeed the lack of quoting.
=
The lack of space I mentioned earlier, in the config text li= teral, is fine.

David J.

--0000000000000c370b062dc74920--