Re: plpgsql memory leaks

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql memory leaks
Date: 2024-01-12 12:35:24
Message-ID: CAFj8pRB132dKbwZtdEZtxnzXmEW9qrOmnuEpk2rxm9V3fpDFcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pá 12. 1. 2024 v 11:54 odesílatel Michael Banck <mbanck(at)gmx(dot)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(dot)stehule(at)gmail(dot)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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2024-01-12 13:23:26 Re: Show WAL write and fsync stats in pg_stat_io
Previous Message shveta malik 2024-01-12 12:19:57 Re: Synchronizing slots from primary to standby