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 1vEBXf-006qtA-T5 for pgsql-bugs@arkaria.postgresql.org; Wed, 29 Oct 2025 19:09:07 +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 1vEBXd-003C2Z-PK for pgsql-bugs@arkaria.postgresql.org; Wed, 29 Oct 2025 19:09:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEBXd-003C2Q-FJ for pgsql-bugs@lists.postgresql.org; Wed, 29 Oct 2025 19:09:04 +0000 Received: from relay8-d.mail.gandi.net ([217.70.183.201]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vEBXZ-004w1S-23 for pgsql-bugs@lists.postgresql.org; Wed, 29 Oct 2025 19:09:03 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 98FFC43B8D; Wed, 29 Oct 2025 19:08:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1761764940; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HyDs9kQgwxES4zwuzzVRnxhBtK8TOqmrgT3hC35F03s=; b=Kzna99bCzvAaU5V69vw9srAKlEu6+UVsEvwxb37B1NQW9U4L8w6/kGBx+FLH4OdDt6UZYL 88YMe6lqU54Tw0HN+YprJc4DRIp2ouM/8r8BiDTPxfYn8SZZiro/Z2phdkcR7hUnurLCC2 xwjbwfE7ekujw8y/x7zL0bSvmgV7kYY0rI0VA/in5forq9mb6KnmPNUYRXytCrieRhgQUy 40cv/WZ8h2D8y49c3KrwDH2mz+DRWNulOMICYtAudoqz87zzbbqKj+qugjIj9z82XKfkYt xhNN2Yaq+VZw8V0OovpIjTL3JB5KhbDFvN4j6S0wNnI1Hx87yTfUXviy7rwBSg== Message-ID: <04c36177-74fc-4d4e-b492-e3d00099190e@vondra.me> Date: Wed, 29 Oct 2025 20:08:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages To: szmscy4nfxk@protonmail.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form References: <19096-9c7bdf8a427906f3@postgresql.org> Content-Language: en-US From: Tomas Vondra In-Reply-To: <19096-9c7bdf8a427906f3@postgresql.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-State: clean X-GND-Score: 0 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdduieegheefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomhepvfhomhgrshcugghonhgurhgruceothhomhgrshesvhhonhgurhgrrdhmvgeqnecuggftrfgrthhtvghrnhepueejvefhteevledvlefgtdevhfeklefhtdfhvdeukeettdelieeifeetveegtdelnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucfkphepkeeirdegledrvdeftddrvddtieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeekiedrgeelrddvfedtrddvtdeipdhhvghloheplgdutddrudefjedrtddrvdgnpdhmrghilhhfrhhomhepthhomhgrshesvhhonhgurhgrrdhmvgdpnhgspghrtghpthhtohepfedprhgtphhtthhopehsiihmshgthiegnhhfgihksehprhhothhonhhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdgsuhhgsheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhgpdhrtghpthhtohepnhhorhgvphhlhiesphhoshhtghhrvghsqhhlrdhorhhg X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/28/25 10:37, PG Bug reporting form wrote: > The following bug has been logged on the website: > > Bug reference: 19096 > Logged by: dex terity > Email address: szmscy4nfxk@protonmail.com > PostgreSQL version: 18.0 > Operating system: Debian 12, 13 > Description: > > Thanks for Postgresql > I have been exploring hugepages functionality in PG and other applications, > found out there's actually a worthy performance improvement. The problem is > that while other applications such as libvirt, php all play nice with HP, if > I launch PG with HP then the next apps will show problems, even though the > number of pages is in excess. Without PG it is possible to run any > combination of apps and instances without problems. PG runs happy when alone > or with one libvirt vm. One thing I noticed is PG does not reserve the full > number of pages when started... maybe that's the problem. > Regards > I have no idea what "play nice" means for the other apps. Either there are enough huge pages or not. And if the apps "show problems" after the pages get used by Postgres, I'd not call that "play nice". Postgres does not reserve huge pages (and the documentation makes this fairly clear [1]). Because how would it know how many huge pages to reserve? There can be other stuff running on the system, and we have no idea how much memory / hugepages that may need. [1] https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-HUGE-PAGES -- Tomas Vondra