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 1thLVD-001LTe-R6 for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 04:34:35 +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 1thLVB-001uIE-W7 for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 04:34:34 +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 1thLVB-001uI6-Lv for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 04:34:33 +0000 Received: from mail-yw1-x1131.google.com ([2607:f8b0:4864:20::1131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thLV7-004sUJ-1f for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 04:34:33 +0000 Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-6f6ca9a3425so34065987b3.2 for ; Sun, 09 Feb 2025 20:34:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739162068; x=1739766868; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=X/A+xgJlNNtUpLFFixHJK/JqaiHNPneqm6yL1Vb73WA=; b=lp+VbdRNZ8dk757BFwVF4+VN4OF751ANISL1FhpcyolZVTas3FyxmEckZ2lDEB6Cu/ fvIT+WAuXO0jEJpvdQ/fD4RpWPviB2iRUXhvfjaQNKTqlVRgwYggtoCia6LA9ltjHveC dzXmW4vv7lZahNDUH0BJyBVlCks4B87QCx2NIzJfS+UomPTRhQFQsWFPp/zRK0rmJsRi jGa+w3X6LzWuihocMOfps7JRm6nn96JJYxxAKJCJXSbf1SckI3v8ms6xLPWmb9spWK1J 8XOWFI/panPeRZMIlZSbq0CJIKCLDUZp+AqflsSvdC7WpxAM/KVE8MNj3Hw8HVsQdPT1 M+ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739162068; x=1739766868; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=X/A+xgJlNNtUpLFFixHJK/JqaiHNPneqm6yL1Vb73WA=; b=UruH5ngvwuHTrYCZDHejs3dmeOEwVGBqHHoe1DgcdpvcHE/cbR+dWXPHfv/7vrLuZa czkB88fJrVSPk831GBfTVGmCqO+kNBYMVq4kGL0cPlBkwY/zPDEzH8msAWisVJW0r2De eemMPadvQ8Ms61IxrJqWw+27FoqcCgQ/qjKuzcLg2W77lXDnLzOQt+Z/v+Dg95AgyzQ1 aCoaYS+vZjU992SNu06KLdSiL7qRMngvFAtbUIX4bf08/XYgNG7WXRE6pC7iWy5tCgS/ IufWt3eWVZkY8EMk9djgGtiDXCa5nLEgmdOmcgaqMI7tqJZ8shms9RbYEfyObYHrecpo B8Qg== X-Gm-Message-State: AOJu0YwmE95XdSgYpaySmwtDkxXVOMluMrFk3LWRoWkWCBa7Us9zirvu yiP0dWAEmxEa64AGXRH+QDFTfXkCpyiv9PvfLKu01GcKta2A4LDIzRVypkqpLVv7IanbHjmeZI5 jHEhd7nDrKwSukkGjKCo301/vzTe+j6xr X-Gm-Gg: ASbGncsUj3Sig3jeGqU4HZiubZSFPHikJq1EVn1u4aFaRX9VxdA6x61yN0RrNerM+iI DlzoPmUu1DzMf4KDBqtOrz333MoaNZySB+It8+OPdtR1mhC5+KS9qRZEr24eSMU6aHTAaeWx7kA == X-Google-Smtp-Source: AGHT+IFYF1j78CfXn/moGfQ7vhoQ5FHlDCKi801xnwd6zyiKvnSyX3/kvz+UYRPmZ0AXDounQgGUxTUJIe3FXhdFVzI= X-Received: by 2002:a05:690c:3809:b0:6ef:7d1e:bffd with SMTP id 00721157ae682-6f9b2a04e21mr119715907b3.37.1739162068159; Sun, 09 Feb 2025 20:34:28 -0800 (PST) MIME-Version: 1.0 From: Mukesh Tanuku Date: Mon, 10 Feb 2025 10:04:17 +0530 X-Gm-Features: AWEUYZnATGM1AswkcDmXAI0qRDYY-JQSBuWskQjJLq_1v8EStSRaNxbxQV4HKFY Message-ID: Subject: PG-15.6: timeout parameters erroring out To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000004798b3062dc239ac" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004798b3062dc239ac Content-Type: text/plain; charset="UTF-8" Hello team, We unabled the postgres timeout parameters in the postgresql.conf file *idle_in_transaction_session_timeout = '1min'idle_session_timeout = '5min'* other way also, like below *idle_in_transaction_session_timeout = 60000idle_session_timeout = 300000* we see these errors reporting in the logs after we enabled those parameters *log:* 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 2025-02-10 04:17:19.845 GMT [2467575] ERROR: trailing junk after numeric literal at or near "1m" at character 43 2025-02-10 04:17:19.845 GMT [2467575] STATEMENT: SET idle_in_transaction_session_timeout = 1min ... ... ... 2025-02-10 04:22:00.823 GMT [2468337] ERROR: trailing junk after numeric literal at or near "5m" at character 28 2025-02-10 04:22:00.823 GMT [2468337] STATEMENT: SET idle_session_timeout = 5min 2025-02-10 04:22:03.487 GMT [2468342] ERROR: trailing junk after numeric literal at or near "5m" at character 28 2025-02-10 04:22:03.487 GMT [2468342] STATEMENT: SET idle_session_timeout = 5min 2025-02-10 04:22:04.470 GMT [2468345] ERROR: trailing junk after numeric literal at or near "5m" at character 28 Is there any know issue/bug with these paramters, can someone help me to get this worked since our app idle connections are getting pilled up and reaching max connections. I really appreciate your help. Thank you. Regards Mukesh Tanuku --0000000000004798b3062dc239ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello team,

We unabled the postgres tim= eout parameters in the postgresql.conf file

= idle_in_transaction_session_timeout =3D '1min'
idle_session_time= out =3D '5min'

other way also,= like below=C2=A0
idle_in_transaction_session_timeout =3D 6= 0000
idle_session_timeout =3D 300000

=
we see these errors reporting in the logs after we enabled those param= eters
log:
2025-02-10 04:17:19.156 GMT [2467573]= ERROR: =C2=A0trailing junk after numeric literal at or near "1m"= at character 43
2025-02-10 04:17:19.156 GMT [2467573] STATEMENT: =C2=A0= SET idle_in_transaction_session_timeout =3D 1min
2025-02-10 04:17:19.845= GMT [2467575] ERROR: =C2=A0trailing junk after numeric literal at or near = "1m" at character 43
2025-02-10 04:17:19.845 GMT [2467575] STA= TEMENT: =C2=A0SET idle_in_transaction_session_timeout =3D 1min
...
...
...

2025-02-10 04:22:00.823 GMT= [2468337] ERROR: =C2=A0trailing junk after numeric literal at or near &quo= t;5m" at character 28
2025-02-10 04:22:00.823 GMT [2468337] STATEME= NT: =C2=A0SET idle_session_timeout =3D 5min
2025-02-10 04:22:03.487 GMT = [2468342] ERROR: =C2=A0trailing junk after numeric literal at or near "= ;5m" at character 28
2025-02-10 04:22:03.487 GMT [2468342] STATEMEN= T: =C2=A0SET idle_session_timeout =3D 5min
2025-02-10 04:22:04.470 GMT [= 2468345] ERROR: =C2=A0trailing junk after numeric literal at or near "= 5m" at character 28

Is there any know iss= ue/bug with these paramters, can someone help me to get this worked since o= ur app idle connections are getting pilled up and reaching max connections.= =C2=A0

I really appreciate your help. Thank you.

Regards
Mukesh Tanuku
--0000000000004798b3062dc239ac--