PostgreSQL: set effective_cache_size and increase max_connections #428
Conversation
This file contains 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
The first configuration change was found to be the critical parameter during the Rocky Linux 9 migration. The second one was bumped during the work on test122
will-moore
approved these changes
Jul 1, 2024
There was a problem hiding this comment.
Looks good.
cache size matches change in https://github.com/IDR/deployment/pull/424/files and the max_connections corresponds to changes as discussed by IDR team. 👍
|
Closing in favor of #424 which will is expected to be deployed on the next production |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 first configuration change was found to be the critical parameter modified during the Rocky Linux 9 migration. The maximal number of connections was bumped during the work on test122
For the next release, we might want to resurrect the work on #424 but the underlying Ansible changes requires additional assessment. In the scope of the
prod122release, this should contain the minimal set of PostgreSQL variable changes to allow deployments without manually copying a configuration file over.