From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Hughes <dhughes20@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: tcp_keepalives settings not being set
In-reply-to: 
 <CAFTBbFBdZ=-o6Q_mHe8oYJk=S2eGNxWx2B23w7VWCmXNchs3Mw@mail.gmail.com>
References: 
 <CAFTBbFBdZ=-o6Q_mHe8oYJk=S2eGNxWx2B23w7VWCmXNchs3Mw@mail.gmail.com>
Comments: In-reply-to Dave Hughes <dhughes20@gmail.com>
	message dated "Wed, 04 Dec 2019 09:33:50 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <17946.1575471250.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Wed, 04 Dec 2019 09:54:10 -0500
Message-ID: <17947.1575471250@sss.pgh.pa.us>
Precedence: bulk

Dave Hughes <dhughes20@gmail.com> writes:
> We have PostgreSQL 10.5 installed on RHEL 6 and I’m new to both.  I’m in
> the process of completing STIGs (Security Technical Implementation Guides)
> for the Department of Defense.  One of the STIGs mentions that we must
> ensure our tcp_keepalives settings are configured in the postgresql.conf
> file.  I currently have these settings set to:
> Tcp_keepalives_idle = 60
> Tcp_keepalives_interval = 60
> Tcp_keepalives_count = 2
> I restarted the database and then ran SHOW_ALL; but it showed all 3
> parameters set to 0.

These will read as zeroes if you're using a non-TCP connection (ie
Unix socket).  Try it after "psql -h localhost" instead of just "psql".

			regards, tom lane