From: Tom Lane <tgl@sss.pgh.pa.us>
To: aditya desai <admad123@gmail.com>
Cc: Pgsql Performance <pgsql-performance@lists.postgresql.org>
Subject: Re: Connection forcibly closed remote server error.
Date: Wed, 15 Feb 2023 09:58:01 -0500
Message-ID: <2082556.1676473081@sss.pgh.pa.us> (raw)
In-Reply-To: <CAN0SRDGF=TWLTa+rNg_yfWAr8DuU+MJtGD-4W8osSvdZgQFjkg@mail.gmail.com>
References: <CAN0SRDGF=TWLTa+rNg_yfWAr8DuU+MJtGD-4W8osSvdZgQFjkg@mail.gmail.com>
aditya desai <admad123@gmail.com> writes:
> We are getting this error when transferring data using COPY command or
> running workflow for huge data. We are using Password Authentication(LDAP)
> "Connection forcibly closed remote server"
Network timeout perhaps? If so, setting more-aggressive TCP keepalive
parameters might help.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, admad123@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Connection forcibly closed remote server error.
In-Reply-To: <2082556.1676473081@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox