On Thu, May 27, 2021 at 8:27 AM Peter Geoghegan <[email protected]> wrote: > > On Wed, Mar 24, 2021 at 10:34 PM Ashutosh Bapat > <[email protected]> wrote: > > Hi All, > > We saw OOM in a system where WAL sender consumed Gigabttes of memory > > which was never released. Upon investigation, we found out that there > > were many ReorderBufferToastHash memory contexts linked to > > ReorderBuffer context, together consuming gigs of memory. They were > > running INSERT ... ON CONFLICT .. among other things. A similar report > > at [1] > > What is the relationship between this bug and commit 7259736a6e5, > dealt specifically with TOAST and speculative insertion resource > management issues within reorderbuffer.c? Amit? >
This seems to be a pre-existing bug. This should be reproduced in PG-13 and or prior to that commit. Ashutosh can confirm? -- With Regards, Amit Kapila.
