| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Kurt Roeckx <kurt(at)roeckx(dot)be>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16707: Memory leak |
| Date: | 2021-04-07 16:28:35 |
| Message-ID: | 20210407162835.GB2857@ahch-to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Nov 10, 2020 at 05:38:08PM -0800, Andres Freund wrote:
> Hi,
>
> On 2020-11-10 23:45:16 +0100, Kurt Roeckx wrote:
> > On Tue, Nov 10, 2020 at 08:50:39PM +0100, Kurt Roeckx wrote:
> > > > There's one known (slow) memory leak in the JIT code / LLVM. Could you
> > > > check if the issue vanishes if you disable JIT (jit = 0)?
> > >
> > > I've just restarted it with jit = 0.
> >
> > It's been about 3 hours since the restart, and it looks much
> > better, it seems to be solved.
>
> Hm, darn. Any chance you could check if the leak is present if you turn
> on jit again, but disable inlining with jit_inline_above_cost=-1? If
> that still fixes the leak I think I know the issue / have a reproducer
> already...
>
I was bit by this too while testing something. I thought it could have been
a problem caused by the support of llvm 12? but given that this report
is for pg12, it seems this is older than that.
should we document it somewhere?
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-04-07 16:31:54 | Re: BUG #16707: Memory leak |
| Previous Message | Julien Rouhaud | 2021-04-07 12:08:56 | Re: BUG #16953: OOB access while converting "interval" to char |