Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tAsJg-000aAp-KT for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Nov 2024 14:56:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tAsJe-007Djx-1d for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Nov 2024 14:56:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tAsJd-007Db2-KT for pgsql-bugs@lists.postgresql.org; Tue, 12 Nov 2024 14:56:26 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tAsJa-001VC5-BU for pgsql-bugs@lists.postgresql.org; Tue, 12 Nov 2024 14:56:24 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 87E8916FB09 for ; Tue, 12 Nov 2024 15:56:18 +0100 (CET) Received: from s934.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 6C30516EB38; Tue, 12 Nov 2024 15:56:18 +0100 (CET) Received: from s474.loopia.se (unknown [172.22.191.6]) by s934.loopia.se (Postfix) with ESMTP id 6A3117CEA4B; Tue, 12 Nov 2024 15:56:18 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s899.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id Ae_LxlRUPvBj; Tue, 12 Nov 2024 15:56:18 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s899.loopia.se (Postfix) with ESMTPSA id D47DD2C8BA6D; Tue, 12 Nov 2024 15:56:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1731423377; bh=4ui/2bfzgEpYUa+M/l0dogNChnlGuJcEu2tF4mnSDbw=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=WwXaJIYYI9NKpZXcYWolf2iAHetZ3CuidaczieNel1mUCakvEjiFxxmnq21/TfOLs 1Dice4HJDJkbpI8w2dQStDVpEIfyvkuyUwz96hf9kBmdZ1wjUNu+DFT4+hEZupLplQ RDBGpJi8yJfpfEpzzkueeHfhRWQDRJzAP/FEKMcwOmndz55+79rzZbp4HzaC6EY+o9 Vzj/9HOKb004eRA4gKn5dcWBTYBk7vuMkfWG7jxeQt6rR/yDGn25lqUq3PZ2lOoQbp E8/qdb6CrIGP31orshx9LRlG9Rxl07GPUri0oNhcLIJpge4ZN3BIh3B7REj0am13FV 5AylFwoSz7I2w== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: BUG #18675: Postgres is not realasing memory causing OOM From: Daniel Gustafsson In-Reply-To: Date: Tue, 12 Nov 2024 15:56:07 +0100 Cc: Tomas Vondra , "David G. Johnston" , "pgsql-bugs@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <5B1E7108-CB1F-4CE9-AC09-2C9299C097C2@yesql.se> References: <18675-39a45505fb472bf0@postgresql.org> <60f459d7-9cfc-4417-8944-a44581edbe4d@gmail.com> <9ce91971-2771-4b3c-aad4-b3d5b952d5d1@vondra.me> <5232B290-5C90-4819-A0F6-A07DE14A20C4@yesql.se> To: Maciej Jaros X-Mailer: Apple Mail (2.3776.700.51.11.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 8 Nov 2024, at 11:29, Maciej Jaros wrote: >=20 > I can now confirm that JIT is adding significant amount of memory on = top of what PG SQL is using. Memory reserved by PG still grows every = day, but doesn't grow as much as with JIT. So there is still something = wrong with Postgres. Using memory isn't necessarily something wrong, it would be a lot worse = if it needed the memory and used swap instead. Are you able to try with JIT = inlining turned off as I asked about upthread. -- Daniel Gustafsson