Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcp1A-0003pe-7b for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Nov 2020 12:14:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kcp19-0002Ze-4U for pgsql-bugs@arkaria.postgresql.org; Wed, 11 Nov 2020 12:14:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcp18-0002ZX-VJ for pgsql-bugs@lists.postgresql.org; Wed, 11 Nov 2020 12:14:26 +0000 Received: from excelsior.roeckx.be ([2a05:7300:0:100::3]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcp16-0002OQ-3b for pgsql-bugs@lists.postgresql.org; Wed, 11 Nov 2020 12:14:25 +0000 Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by excelsior.roeckx.be (Postfix) with ESMTP id CEEAAA8A00B1; Wed, 11 Nov 2020 12:14:20 +0000 (UTC) Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 8C1D31FE0DC9; Wed, 11 Nov 2020 13:14:20 +0100 (CET) Date: Wed, 11 Nov 2020 13:14:20 +0100 From: Kurt Roeckx To: Andres Freund Cc: Tom Lane , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16707: Memory leak Message-ID: <20201111121420.GA666413@roeckx.be> References: <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> <20201111013808.4cev55uxq32bd6dd@alap3.anarazel.de> <20201111094918.GH391173@roeckx.be> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201111094918.GH391173@roeckx.be> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Nov 11, 2020 at 10:49:18AM +0100, Kurt Roeckx wrote: > > 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've just restarted it with > jit=1 > jit_inline_above_cost=-1 So after more than 2 hours, I see no leak with those settings. Kurt