Re: Connection forcibly closed remote server error.

From: aditya desai <admad123(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Connection forcibly closed remote server error.
Date: 2023-02-15 18:55:21
Message-ID: CAN0SRDHjU79AA8+FFTnvwS+roYtEg_yVxhnvJbCRXMX81rJr5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi Jeff,
Apologies. Here is how the message actually looks like.

could not receive data from client: An existing connection was forcibly
closed by the remote host.

All links from Google pointing towards Connection Pooling. However it has
been implemented from the application side.

Regards,
Aditya.

On Thu, Feb 16, 2023 at 12:07 AM Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> On Wed, Feb 15, 2023 at 7:13 AM aditya desai <admad123(at)gmail(dot)com> wrote:
>
>> Hi,
>> 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"
>>
>
> Are you sure that that is the exact wording? It doesn't sound like grammar
> that would be used for an error message. Or did you perhaps translate it
> to English from a localized error message?
>
> Is that error reported by the client, or in the server log? Whichever end
> that is, what does the other end say?
>
> Cheers,
>
> Jeff
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ranier Vilela 2023-02-15 19:02:01 Re: Connection forcibly closed remote server error.
Previous Message Jeff Janes 2023-02-15 18:36:48 Re: Connection forcibly closed remote server error.