Re: client waits for end of update operation and server proc is idle

Karsten Hilbert <Karsten.Hilbert@gmx.net> writes:
> Am Sun, Apr 25, 2021 at 01:21:25PM -0400 schrieb Tom Lane:
>> Still, the apparent message length is then "RP-2" (0x52502d32)
>> which is bigger than 1GB so I don't quite understand why you didn't
>> get an "out of memory" error.

> But he did, didn't he ?

Those log messages do appear to match the theory, but in the case at
hand, the server seems to have hung up without throwing any error.

However, we'd reproduce that if the apparent "message length" was
less than 1GB (assuming the server process could malloc that much
memory).  That'd occur for any second byte less than 0x40, such
as an ASCII digit.

            regards, tom lane