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

From Matthias Apitz
Subject Re: client waits for end of update operation and server proc is idle
Date
Msg-id YIXhVUsZP4UaJopA@c720-r368166.fritz.box
Whole thread Raw
In response to client waits for end of update operation and server proc is idle  (Matthias Apitz <guru@unixarea.de>)
List pgsql-general
El día domingo, abril 25, 2021 a las 08:05:21p. m. +0200, Karsten Hilbert escribió:

> > > > The serverlog has around this time (sorry for German):
> > > >
> > > > 2021-04-23 05:55:23.591 CEST [2317] LOG:  unvollständige Message vom Client
> 
>     "incomplete message from client"
> 
> > > > 2021-04-23 05:55:23.593 CEST [2317] FEHLER:  Speicher aufgebraucht
> 
>     "memory exhausted"
> 
> > > > 2021-04-23 05:55:23.593 CEST [2317] DETAIL:  Kann Zeichenkettenpuffer mit 0 Bytes nicht um 1380986158 Bytes
vergrößern.
> 
>     "cannot extend 0-byte string buffer by 1380986158 bytes"
> 
> > > > 2021-04-23 05:55:23.593 CEST [2317] LOG:  konnte Daten nicht an den Client senden: Datenübergabe unterbrochen
(brokenpipe)
 
> 

These messages at 05:55:xx are caused by our automatic deployment of the
software every day which starts at 05:55:00 by cron and short after installing all
software all servers (the PostgreSQL clients) get stopped (i.e. killed)
and restarted. The hung appears a few minutes later at 05:57:xx.

    matthias
-- 
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub



pgsql-general by date:

Previous
From: Robert Treat
Date:
Subject: Re: impact of version upgrade on fts
Next
From: Matthias Apitz
Date:
Subject: Re: client waits for end of update operation and server proc is idle