Actually set MEMORY_LIMIT_IN_BYTES based on cgroups limits #427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
in common.sh
POSTGRESQL_SHARED_BUFFERS
andPOSTGRESQL_EFFECTIVE_CACHE_SIZE
are calculated based onMEMORY_LIMIT_IN_BYTES
(if set).But I don't see
MEMORY_LIMIT_IN_BYTES
set anywhere and it doesn't seem to be set automatically in a container with memory limits specified (for example in Openshift/k8s or when you run a container via podman/docker and specify--memory
).FYI: I'm experimenting with memory-related settings because I'm seeing #396 (postgresql-12-centos7) and have no idea what else to try.