Re: BUG #16707: Memory leak
От | Andres Freund |
---|---|
Тема | Re: BUG #16707: Memory leak |
Дата | |
Msg-id | 7acc8678-df5f-4923-9cf6-e843131ae89d@www.fastmail.com обсуждение исходный текст |
Ответ на | BUG #16707: Memory leak (PG Bug reporting form <noreply@postgresql.org>) |
Список | pgsql-bugs |
Hi, On Wed, Apr 7, 2021, at 09:28, Jaime Casanova wrote: > 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. I hope to fix it soon - I have two different mostly working fixes. I'll get back to it once the dust around the freeze settles. Andres
В списке pgsql-bugs по дате отправления: