Horton

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

Matthias Otterbach <mo@otterbach.eu>

View thread View on postgr.es
From: Matthias Otterbach <mo@otterbach.eu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Janes <jeff.janes@gmail.com>, Andres Freund <andres@anarazel.de>, pgsql-bugs@lists.postgresql.org
Date: 2019-03-19T07:08:52Z
Lists: pgsql-bugs 
Dear all,

On 2019-03-18 23:00, Tom Lane wrote:
> I wrote:
>> Yup; the attached fixes it.  Will push after a bit more testing.
> 
> Done now, but I forgot to credit Jeff in the commit message.
> My apologies for that (too bad it's impossible to edit commit
> messages after the fact).

thanks a lot for your replies and the quick fix, I also re-tested it 
just now (compiling from the current 11 branch) and could not reproduce 
my memory issue anymore.

Thanks again, best regards
Matthias Otterbach

Commits

  1. Fix memory leak in printtup.c.

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