From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Abraham, Danny" <danny_abraham@bmc.com>
cc: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Can't change tcp_keepalives_idle
In-reply-to: <SJ2PR02MB97060CFEDBDE9FC11F1844358EBD2@SJ2PR02MB9706.namprd02.prod.outlook.com>
References: <SJ2PR02MB97060CFEDBDE9FC11F1844358EBD2@SJ2PR02MB9706.namprd02.prod.outlook.com>
Comments: In-reply-to "Abraham, Danny" <danny_abraham@bmc.com>
	message dated "Sun, 04 Aug 2024 11:16:21 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <399788.1722786198.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 04 Aug 2024 11:43:18 -0400
Message-ID: <399789.1722786198@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/399789.1722786198%40sss.pgh.pa.us>
Precedence: bulk

"Abraham, Danny" <danny_abraham@bmc.com> writes:
> Change tcp_keepalives_idle in postgresql.conf from 0 to 300 , then pg_ct=
l reload but it stays with the old 0 value.
> Tried restart and it did not work. PG Log says it was changed.

tcp_keepalives_idle isn't implemented on all platforms.  But I'd
expect to see a LOG message in the postmaster log about that, either
something about "setsockopt failed" or "WSAIoctl failed" or "setting
the keepalive idle time is not supported".

Also, if you inquire the value on a non-TCP connection, you'll
get zero because it's not relevant.

			regards, tom lane