From: Tom Lane <tgl@sss.pgh.pa.us>
To: fran.tm213@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17776: Connections are terminated unexpectedly sometimes
In-reply-to: <17776-36d858c9afa20043@postgresql.org>
References: <17776-36d858c9afa20043@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 06 Feb 2023 11:17:13 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2665709.1675697999.1@sss.pgh.pa.us>
Date: Mon, 06 Feb 2023 10:39:59 -0500
Message-ID: <2665710.1675697999@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2665710.1675697999%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I am running Ruby on Rails app with postgresql 14.6 on ubuntu 20.
> For some reason, the connections are terminated unexpectedly while running a
> background job.
> Regarding background job, it requires around 100~200 connections over
> 6~7hrs.
> I've checked postgresql log around that time.
> 2023-02-06 06:45:41.702 UTC [341438] user@db_production LOG:  could not
> receive data from client: Connection reset by peer
> 2023-02-06 08:26:56.134 UTC [352190] user@db_production LOG:  could not
> receive data from client: Connection reset by peer
> 2023-02-06 08:26:56.134 UTC [352191] user@db_production LOG:  could not
> receive data from client: Connection reset by peer

Looks like something in your network infrastructure is timing out
and dropping idle connections too quickly.  If you can't fix the
actual problem, Postgres' TCP-timeout settings might provide a
workaround by maintaining an illusion that the connection is
busy.  See

 tcp_keepalives_count
 tcp_keepalives_idle
 tcp_keepalives_interval
 tcp_user_timeout

			regards, tom lane