Re: unconstrained memory growth in long running procedure stored procedure after upgrading 11-12 - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: unconstrained memory growth in long running procedure stored procedure after upgrading 11-12
Date
Msg-id CAHyXU0xtTcCVsPuT21kVE+RjE9zVMFZRLi6Pg1T5G=u09nx79Q@mail.gmail.com
Whole thread Raw
In response to Re: unconstrained memory growth in long running procedure stored procedure after upgrading 11-12  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Mar 30, 2021 at 7:14 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Justin Pryzby <pryzby@telsasoft.com> writes:
> > On Tue, Mar 30, 2021 at 04:17:03PM -0500, Merlin Moncure wrote:
> >> We just upgraded from postgres 11 to 12.6 and our server is running
> >> out of memory and rebooting about 1-2 times a day.
>
> > I haven't tried your test, but this sounds a lot like the issue I reported with
> > JIT, which is enabled by default in v12.
>
> FWIW, I just finished failing to reproduce any problem with that
> test case ... but I was using a non-JIT-enabled build.

Yep.  Disabling jit (fully, fia jit=off, not what was suggested
upthread) eliminated the issue, or at least highly mitigated the leak.
I was using pgdg rpm packaging, which enables jit by default.  Thanks
everyone for looking at this, and the workaround is quick and easy.

merlin



pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: cursor already in use, UPDATE RETURNING bug?
Next
From: Kohei KaiGai
Date:
Subject: Re: TRUNCATE on foreign table