From: Tom Lane <tgl@sss.pgh.pa.us>
To: 66666666nikita@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17179: EOF detected
In-reply-to: <17179-100f778969bdc589@postgresql.org>
References: <17179-100f778969bdc589@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 03 Sep 2021 05:47:15 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2481801.1630676065.1@sss.pgh.pa.us>
Date: Fri, 03 Sep 2021 09:34:25 -0400
Message-ID: <2481802.1630676065@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2481802.1630676065%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Query running for more than 30 minutes are disconnected
> SELECT pg_sleep(1820)
> SSL SYSCALL error: EOF detected

Ideally, you'd fix your broken network infrastructure.  However,
if you can't ...

> Increased timeouts tcp_user_timeout, tcp_keepalives_interval didn't help.

... that's exactly backwards about how to work around it.  You need
to *reduce* the interval at which keepalives are sent.  Try setting
tcp_keepalives_idle to 10min or so.  (At least on my Linux box,
it seems to default to 7200s = 2 hours, so that it's no surprise that a
router that drops connections after 30 minutes would cause problems.)

			regards, tom lane