Re: plpgsql memory leaks - Mailing list pgsql-hackers

From Michael Banck
Subject Re: plpgsql memory leaks
Date
Msg-id 65a14469.050a0220.fead0.7c6d@mx.google.com
Whole thread Raw
In response to Re: plpgsql memory leaks  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: plpgsql memory leaks
List pgsql-hackers
Hi,

On Fri, Jan 12, 2024 at 01:35:24PM +0100, Pavel Stehule wrote:
> pá 12. 1. 2024 v 11:54 odesílatel Michael Banck <mbanck@gmx.net> napsal:
> > 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 got that wrong, it needs to be -1 to disable it.

But if you are already running the master branch, it is probably a
separate issue.


Michael



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed
Next
From: Aleksander Alekseev
Date:
Subject: Re: reorganize "Shared Memory and LWLocks" section of docs