Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak) - Mailing list pgsql-bugs

From Jeff Janes
Subject Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak)
Date
Msg-id CAMkU=1x_XySqXZ-1gCyoaipKLzefQSr1BuaHL12vy_9WKFnjYQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak)  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak)  (Andres Freund <andres@anarazel.de>)
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>)
List pgsql-bugs
Tree view
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.

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage when selecting BYTEA data (maybe memory leak)
Next
From: Andres Freund
Date:
Subject: Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak)