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 1thM2T-001REG-Dy for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 05:08:57 +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 1thM2R-002MQT-PV for pgsql-general@arkaria.postgresql.org; Mon, 10 Feb 2025 05:08:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1thM2R-002MQF-Ah for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 05:08:55 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1thM2P-004Gkz-0p for pgsql-general@lists.postgresql.org; Mon, 10 Feb 2025 05:08:54 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2adc2b6837eso1260974fac.1 for ; Sun, 09 Feb 2025 21:08:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739164133; x=1739768933; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=aCEpC26MVsi4brt6I/NFR2RWkfOuL9Zn0D5G7YSzNoo=; b=krfu5fzsyuW39Vudy5JpsZaQYX7iQjaI4JkckwtEumka9RwRMqvST9IaqMH52tU1sV vIyP/ViVF94N2yf4VGJPF+NLCNyyEvUgipVXWn359mpj8+phWVd5OP4KQW0ivPsz9ypu gB8cvBoEBsadFx9/aWjVnA8Lf7s9uX509uCrBzGYnocWyp2vdqdBM0WADbRfWQfVlCQU 0pmlAnr7dYhHiG+3nWjxw4Z+ouaLcNSE1LVlLYt0r8Eb103EjP1S8EU6GbKLchWnzsnL hA7IlckftkJnSadfG8RZRBwb7JCn6HBtpufFurBL2GvFai5fUU02UgJv/RiEsNy5kcg6 OX9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739164133; x=1739768933; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=aCEpC26MVsi4brt6I/NFR2RWkfOuL9Zn0D5G7YSzNoo=; b=gI1gh5/ZzQFj9qPVSRFaLchk7DFEQ0tOBPIO/6cNICitS00tTFIU45vxzNnHvDd9KP 6/6IudR3k2BrzbxX2tv14PBozGVvsiYYiJd23VdG+cS23QPJJ3nUW3llQMWos/CdAOW5 3G/3KZe6ze0jTwdxreFyot94Y9ryRT3VfB5kFi40h1/Dlkg1STZIq7tQlo6EnIRGsFLi UNlK+9SAc+M+HID3+4P+AOblJc5cg3Pu2dmiLCSLZw1Q0kxNapBdmH+QKWMdapZXaTDt rHIlq95cuA4ar/Af0QhH2nnT2V2hg3aCEqwb3AqWR2HVMk9BW4yOUtXRVMmPLsX1YOGb /Grg== X-Forwarded-Encrypted: i=1; AJvYcCWODAIv4N1liLHYdQIbK9YPZD02caG2GbuELNpfmu9bquf3Bb4MY+Nejt/O9t5Jz8dMokxN3mAKSJ0We5k4@lists.postgresql.org X-Gm-Message-State: AOJu0Ywo3FItxtDrwT1BbgG1nYtfUV4IzF42aTYIEWinnpZpIFdJ5J3q y1g3O5/W7kTLwhY1xhYD3M6JbtjEnAYfEKnuUT4eRpWeetn09kNToWD2BmP9TwdQDDQAZm+LBvG moLvR0SPYGVX1iYeCK105/bp12k8= X-Gm-Gg: ASbGncvuOS1YKgh/CYCsZdK6vJ1BUGkLJ9q16jmw1nkgNv9D54z0iBNk43COKVINCBw Vc2E8k/WwFCBLQieiicf1tejv0fwPqP/Spj+Ywm4Tn7dHl/klPwGPm7u7SvTCCItrW/BEIgA= X-Google-Smtp-Source: AGHT+IF/Oxp40UnCGKM9Ow0uFBhhjzlISmlbJQhuTVHuhhStStfWs2u1aNAsiPZ6i2FL5QzRKX+Uk1KuIKI8j5KIzbA= X-Received: by 2002:a05:6871:3a0d:b0:29e:503a:7ea3 with SMTP id 586e51a60fabf-2b83ef36650mr7916468fac.36.1739164133060; Sun, 09 Feb 2025 21:08:53 -0800 (PST) MIME-Version: 1.0 Received: by 2002:ac9:5890:0:b0:587:17f7:65da with HTTP; Sun, 9 Feb 2025 21:08:52 -0800 (PST) In-Reply-To: <2106557.1739163733@sss.pgh.pa.us> References: <2106557.1739163733@sss.pgh.pa.us> From: "David G. Johnston" Date: Sun, 9 Feb 2025 22:08:52 -0700 X-Gm-Features: AWEUYZnFIX8eWhLeEp_xshZYzcoEc6A4vNqXVVBpamq8G_I0IfJ83Uq-udiaIok Message-ID: Subject: Re: PG-15.6: timeout parameters erroring out To: Tom Lane Cc: Mukesh Tanuku , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000005b78eb062dc2b450" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005b78eb062dc2b450 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 are = indeed the lack of quoting. The lack of space I mentioned earlier, in the config text literal, is fine. David J. --0000000000005b78eb062dc2b450 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, February 9, 2025, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Muke= sh Tanuku <mukesh.postgres@= gmail.com> writes:
> We unabled the postgres timeout parameters in the postgresql.conf file=

> *idle_in_transaction_session_timeout =3D '1min'idle_sessi= on_timeout =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 something.

=
I do agree too much is missing here.=C2=A0 The 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 literal, is fine.

David J.

--0000000000005b78eb062dc2b450--