Re: plpgsql memory leaks
| От | Pavel Stehule |
|---|---|
| Тема | Re: plpgsql memory leaks |
| Дата | |
| Msg-id | CAFj8pRB132dKbwZtdEZtxnzXmEW9qrOmnuEpk2rxm9V3fpDFcw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: plpgsql memory leaks (Michael Banck <mbanck@gmx.net>) |
| Ответы |
Re: plpgsql memory leaks
|
| Список | pgsql-hackers |
pá 12. 1. 2024 v 11:54 odesílatel Michael Banck <mbanck@gmx.net> napsal:
Hi,
On Fri, Jan 12, 2024 at 11:02:14AM +0100, Pavel Stehule wrote:
> pá 12. 1. 2024 v 10:27 odesílatel Pavel Stehule <pavel.stehule@gmail.com>
> napsal:
>
> > Hi
> >
> > I have reported very memory expensive pattern:
[...]
> > takes lot of megabytes of memory too.
>
> The megabytes leaks are related to JIT. With JIT off the memory consumption
> is significantly less although there are some others probably.
I cannot readily reproduce this.
Which version of Postgres is this and on which platform/distribution?
It was tested on master branch (pg 17) on Fedora 39
Did you try keep jit on but set jit_inline_above_cost to 0?
The back-branches have a fix for the above case, i.e. llvmjit memleaks
that can be worked-around by setting jit_inline_above_cost=0.
I'll do recheck
Pavel
Michael
В списке pgsql-hackers по дате отправления: