BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: szmscy4nfxk(at)protonmail(dot)com
Subject: BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages
Date: 2025-10-28 09:37:18
Message-ID: 19096-9c7bdf8a427906f3@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 19096
Logged by: dex terity
Email address: szmscy4nfxk(at)protonmail(dot)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

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2025-10-28 12:44:39 Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
Previous Message Richard Guo 2025-10-28 08:46:52 Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results