Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage when selecting BYTEA data (maybe memory leak)

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Matthias Otterbach <mo@otterbach.eu>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Date: 2019-03-18T20:53:07Z
Lists: pgsql-bugs
Hi,

On 2019-03-18 16:44:02 -0400, Jeff Janes wrote:
> On Mon, Mar 18, 2019 at 2:50 PM Jeff Janes <jeff.janes@gmail.com> wrote:
> 
> >
> > Doing that, I can reproduce the problem, and it seems to be using an
> > implicitly declared cursor (which I have not run into before).
> >
> >
> The culprit is f2dec34e19d3969ddd6.  Also, it doesn't depend on bytea, it
> leaks for text as well.
> 
> I looked at the patch and nothing in jumps out to me as causing a leak.
> 
> commit f2dec34e19d3969ddd616e671fe9a7b968bec812
> Author: Andres Freund <andres@anarazel.de>
> Date:   Wed Oct 11 16:26:35 2017 -0700
> 
>     Use one stringbuffer for all rows printed in printtup.c.

Thanks for figuring that out. On a quick scan I don't see anything
obvious. Let me try this out.

- Andres


Commits

  1. Fix memory leak in printtup.c.

  2. Use one stringbuffer for all rows printed in printtup.c.