Date: Tue, 10 Nov 2020 17:38:08 -0800
From: Andres Freund <andres@anarazel.de>
To: Kurt Roeckx <kurt@roeckx.be>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16707: Memory leak
Message-ID: <20201111013808.4cev55uxq32bd6dd@alap3.anarazel.de>
References: <16707-f5df308978a55bf8@postgresql.org>
 <1999972.1604957673@sss.pgh.pa.us>
 <20201109220329.GC391173@roeckx.be>
 <2002012.1604960437@sss.pgh.pa.us>
 <20201110043127.sfkyvvjqy7x3er5k@alap3.anarazel.de>
 <20201110081120.GF391173@roeckx.be>
 <20201110193517.t5hbqkya67gb23rq@alap3.anarazel.de>
 <20201110195039.GG391173@roeckx.be>
 <20201110224516.GA568918@roeckx.be>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201110224516.GA568918@roeckx.be>
Precedence: bulk

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...

- Andres