From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Bee.Lists" <bee.lists@gmail.com>
cc: Submit Postgresql Novice <pgsql-novice@postgresql.org>
Subject: Re: Connections Increasing Slowly
In-reply-to: <0345AEA7-346C-452F-B3AE-13ED57818F5F@gmail.com>
References: <8A1234E2-D4C3-451F-8F60-901D0D5E0CA5@gmail.com>
 <2088230.1592856708@sss.pgh.pa.us>
 <0345AEA7-346C-452F-B3AE-13ED57818F5F@gmail.com>
Comments: In-reply-to "Bee.Lists" <bee.lists@gmail.com>
	message dated "Mon, 22 Jun 2020 21:57:44 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2114530.1592878045.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Mon, 22 Jun 2020 22:07:25 -0400
Message-ID: <2114531.1592878045@sss.pgh.pa.us>
Precedence: bulk

"Bee.Lists" <bee.lists@gmail.com> writes:
> On Jun 22, 2020, at 4:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Another idea, if you suspect that the idle connections are caused
>> by firewall timeouts or the like, is to enable more aggressive
>> TCP keepalive checking, to ensure the server notices if a client
>> isn't there at all anymore.  See the tcp_keepalives_* settings.

> Who owns the actual connections?  The server allows them, the client
> requests them.  The error I am getting is that the gem I’m using uses a
> connection that’s dropped.

Hmm.  If the client thinks the server dropped the connection, but the
server thinks the connection is still live, that smells strongly of
network-level disconnects.  Does the client let the connection sit idle
for more than a minute or two at a time?  If so I'd bet that some firewall
in between is deciding that the connection is dead and dropping it.
Again, setting the server's tcp_keepalives_* settings could help fix that,
by ensuring that the network connection sees some traffic regularly.

			regards, tom lane