| From: | Michael Banck <mbanck(at)gmx(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql memory leaks |
| Date: | 2024-01-12 10:54:29 |
| Message-ID: | 65a11a66.170a0220.fd97.5da6@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
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.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2024-01-12 11:00:01 | Re: Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed |
| Previous Message | Alvaro Herrera | 2024-01-12 10:32:26 | Re: tablecmds.c/MergeAttributes() cleanup |