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 1thT4m-002nj4-G3 for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 12:39:49 +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 1thT4l-000woF-6r for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 12:39:47 +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 1thT4k-000wo5-08 for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 12:39:46 +0000 Received: from omr012.pc5.atmailcloud.com ([103.150.252.12]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1thT4c-0001yv-13 for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 12:39:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tpg.com.au; s=202309; h=MIME-Version:Content-Type:Date:To:From:Subject:Message-ID; bh=8nixNf6IorOCZ+mDxMZGsDjLlkU/k9+Qc6/PsC00U/g=; b=P+/lavOXXL0TmmVarSiuUrS98U 8OfCld7zYJ9Y8ps9d0ei7YaH6Ljcs0fLLfZ+Vsm288o98Cpzk/rbVX4rHmx8f0a+reCgylHdzW4J/ hiuDtlNDUovmnVbGeSIdkEhOk3kRHUWb2YTi0N+7r1Qhrb4Ccb4/3a3mEpKiR1UkGtyjeWVM1WxNq qKxJvHljbPhbnBrHFNdLRPRqCP4IVmpa9hy/XTg1C6CDidPzWpZ+ZBFS0FLEPvKQVwYe3qngp0rdU 8XOtnXMCpfyUdXmZ/anuHMztmvVPxHKcmrqW272f+OQR05C6sxDdNOXLi0dNgma4rgIurN+ZAgDl6 /eifD2Iw==; Received: from cmr-kakadu02.internal.pc5.atmailcloud.com (cmr-kakadu02.internal.pc5.atmailcloud.com [192.168.1.4]) by omr.internal.pc5.atmailcloud.com (Exim/cmr-kakadu02.i-072ecd3d9c3d786a8) with ESMTPS (envelope-from ) id 1thT4V-000000005Ma-3RPA ; Mon, 10 Feb 2025 12:39:31 +0000 Received: from ([192.168.1.100] [121.45.245.143]) by cmr-kakadu02.internal.pc5.atmailcloud.com (Exim/[192.168.1.100]) with ESMTPSA (envelope-from ) id 1thT4V-000000000lY-2JQd ; Mon, 10 Feb 2025 12:39:31 +0000 Message-ID: <788aca1329878b3fbc93da929bd54b758ec5e4b4.camel@tpg.com.au> Subject: Re: PG-15.6: timeout parameters erroring out From: rob stone To: Mukesh Tanuku , pgsql-general@lists.postgresql.org Date: Mon, 10 Feb 2025 23:39:12 +1100 In-Reply-To: References: <2106557.1739163733@sss.pgh.pa.us> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.54.3-2 MIME-Version: 1.0 X-Atmail-Id: floriparob@tpg.com.au X-atmailcloud-spam-action: no action X-Cm-Analysis: v=2.4 cv=NMrT+V6g c=1 sm=1 tr=0 ts=67a9f383 a=fFtvOYAu0xXLxv59qvQhtQ==:117 a=fFtvOYAu0xXLxv59qvQhtQ==:17 a=IkcTkHD0fZMA:10 a=T2h4t0Lz3GQA:10 a=FVG_Qj_OW4wA:10 a=x7bEGLp0ZPQA:10 a=YBD6otfKczFjrl80UA0A:9 a=QEXdDO2ut3YA:10 X-Cm-Envelope: MS4xfIHgq16BuLNiohhYC7YSpwhzaVLPH+XVHtPk4bu29/dRmSDdaBiWatU1sslLKaDMT0dM179kTSsZAbEy7u1O0VGNU4+gXWxx+w6x1ZCqRSb5W95uvPc5 0NS5YehNed4vpcB4cCXAEK/7e92qC3tk5xjksAUgYekeR3xs01i8vQ99lBoGSy47d0oNKScaoepumw== X-atmailcloud-route: unknown List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2025-02-10 at 16:06 +0530, Mukesh Tanuku wrote: > Thanks for your quick=C2=A0responses. >=20 > 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') >=20 > but i get an immediate error after reloading the configuration file.=C2= =A0 >=20 > postgres.log file > 2025-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=A0parameter > "idle_in_transaction_session_timeout" changed to "80000" > 2025-02-10 10:27:16.117 GMT [2531150] ERROR: =C2=A0trailing junk 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 >=20 > though we are not firing any SQL statements explicitly=C2=A0we see this > error. >=20 > i guess something else is the issue other than spacing. >=20 >=20 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. >=20