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

Поиск

Список

Период

Сортировка

От	Jeff Janes
Тема	Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak)
Дата	18 марта 2019 г. 20:44:02
Msg-id	CAMkU=1x_XySqXZ-1gCyoaipKLzefQSr1BuaHL12vy_9WKFnjYQ@mail.gmail.com обсуждение исходный текст
Ответ на	Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak) (Jeff Janes <jeff.janes@gmail.com>)
Ответы	Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage whenselecting BYTEA data (maybe memory leak) Re: BUG #15700: PG 10 vs. 11: Large increase in memory usage when selecting BYTEA data (maybe memory leak)
Список	pgsql-bugs

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 по дате отправления: