Update description of POSTGRESQL_SHARED_BUFFERS & POSTGRESQL_EFFECTIVE_CACHE_SIZE default values #448
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…E_CACHE_SIZE default values The previous description was not completely correct, because when the container is run in Kubernetes/Openshift, the default values are calculated: https://github.com/sclorg/postgresql-container/blob/master/src/root/usr/share/container-scripts/postgresql/common.sh#L12 based on memory limit: https://github.com/sclorg/container-common-scripts/blob/master/shared-scripts/core/usr/bin/cgroup-limits
phracek
approved these changes
Jul 14, 2022
Member
phracek
left a comment
phracek
left a comment
There was a problem hiding this comment.
Thanks for the updated postgresql documentation.
[test-all]
Member
|
[test-all] |
Member
|
OpenShift 4 failure is not caused by this PR. Let's fix it by the other PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The previous description was not completely correct, because when the container is run in Kubernetes/Openshift, the default values are calculated based on memory limit.