| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Cc: | Matthias Apitz <guru(at)unixarea(dot)de>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: client waits for end of update operation and server proc is idle |
| Date: | 2021-04-25 18:13:36 |
| Message-ID: | 2004841.1619374416@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2021-04-25 19:32:33 | Re: impact of version upgrade on fts |
| Previous Message | Karsten Hilbert | 2021-04-25 18:05:21 | Re: client waits for end of update operation and server proc is idle |