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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kfnAR-0006HE-Ty
	for pgsql-bugs@arkaria.postgresql.org; Thu, 19 Nov 2020 16:52:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1kfnAQ-0000Am-HJ
	for pgsql-bugs@arkaria.postgresql.org; Thu, 19 Nov 2020 16:52:18 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <laurent.mignon@acsone.eu>)
	id 1kfn4F-00074L-DX
	for pgsql-bugs@lists.postgresql.org; Thu, 19 Nov 2020 16:45:55 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by magus.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <laurent.mignon@acsone.eu>)
	id 1kfn4C-0002ot-A9
	for pgsql-bugs@postgresql.org; Thu, 19 Nov 2020 16:45:55 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id 6E14C22D2EB39
	for <pgsql-bugs@postgresql.org>; Thu, 19 Nov 2020 09:45:50 -0700 (MST)
Date: Thu, 19 Nov 2020 09:45:50 -0700 (MST)
From: "laurent.mignon@acsone.eu" <laurent.mignon@acsone.eu>
To: pgsql-bugs@postgresql.org
Message-ID: <1605804350439-0.post@n3.nabble.com>
In-Reply-To: <20201111094918.GH391173@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>
Subject: Re: BUG #16707: Memory leak
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

Hi,

We also encounter this issue on our postgresql12 database. Disabling jit
inlining seems to reduce drastically the memory leak. But after 4 days
without restart (compared to the 3 restart / day before the change)  it
seems that we still have a leak. The RAM is full and the swap almost full.. 
I hope that a fix will land quickly since this issue has a huge impact on
our business.

Regards



--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html