Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Matthias Otterbach <mo@otterbach.eu>, pgsql-bugs@lists.postgresql.org
Date: 2019-03-18T20:16:47Z
Lists: pgsql-bugs 
Jeff Janes <jeff.janes@gmail.com> writes:
> Doing that, I can reproduce the problem, and it seems to be using an
> implicitly declared cursor (which I have not run into before).

Hm, I'd tried a manually declared cursor w/ FETCH commands, but apparently
this way is different.  Thanks for the confirmation.

			regards, tom lane

Commits

  1. Fix memory leak in printtup.c.

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