It might happen that you need to run postgres on a node with hugepages enabled - this is normally not an issue, except you're working with containers, for example within kubernetes/openshift.
In our case we are using mayastor at the storage layer which requires us to enable hugepages. But on the same system also postgres needs to run. Both support huge pages, so it should be fine?
Unfortunately, despite everything should work, postgres has issues starting - it seemingly detects huge pages but fails to allocate these unless you explicitly assign them to the container (https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/).
Add hugepages to resources
The fix is to add a hugepages-limit to the resources:
In this example you can see that we only add the hugepages-2Mi (for 2Mi sized hugepages) directive. Having this enabled, postgres with start right away without any issues (another issue might be shared memory, but that's not part of this post).
Quite an easy fix. If you're interested more in huge pages, check out the following links: