Re: client waits for end of update operation and server proc is idle - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: client waits for end of update operation and server proc is idle
Date
Msg-id YIKLJayazOYWv2RW@hermes.hilbert.loc
Whole thread Raw
In response to Re: client waits for end of update operation and server proc is idle  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
Am Fri, Apr 23, 2021 at 10:48:24AM +0200 schrieb Laurenz Albe:

> > The serverlog has around this time (sorry for German):
> >
> > 2021-04-23 05:55:23.591 CEST [2317] LOG:  unvollständige Message vom Client
> > 2021-04-23 05:55:23.593 CEST [2317] FEHLER:  Speicher aufgebraucht
> > 2021-04-23 05:55:23.593 CEST [2317] DETAIL:  Kann Zeichenkettenpuffer mit 0 Bytes nicht um 1380986158 Bytes
vergrößern.
> > 2021-04-23 05:55:23.593 CEST [2317] LOG:  konnte Daten nicht an den Client senden: Datenübergabe unterbrochen
(brokenpipe) 
> > 2021-04-23 05:55:23.593 CEST [2317] FATAL:  Verbindung zum Client wurde verloren
> > 2021-04-23 05:57:20.339 CEST [27190] LOG:  unerwartetes EOF auf Client-Verbindung mit einer offenen Transaktion
> > 2021-04-23 05:59:17.419 CEST [26827] LOG:  unerwartetes EOF auf Client-Verbindung mit einer offenen Transaktion
> >
> > What else could be checked for this? Any hints about this issue?
>
> It seems pretty clear that both the client and the server are waiting for each other.
>
> The server is of the opinion that it has completed the query, while the client is
> still waiting for the response.
>
> I would look for the problem in the network between both.  The error messages
> (unexpected EOF on client connection, broken pipe) seem to point in the same direction.

It also reports an out-of-memory situation:

>> 2021-04-23 05:55:23.593 CEST [2317] FEHLER:  Speicher aufgebraucht
>> 2021-04-23 05:55:23.593 CEST [2317] DETAIL:  Kann Zeichenkettenpuffer mit 0 Bytes nicht um 1380986158 Bytes
vergrößern.

It seems what is to be sent to the client is "too large".

Following which sending the data seems (intentionally?)
aborted by the server, which the other side likely reports as
loss-of-signal.

Also, where does the "imcomplete message from client"
originate from ?

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B



pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: client waits for end of update operation and server proc is idle
Next
From: Mitar
Date:
Subject: Re: Why is writing JSONB faster than just JSON?