postgresql: Use config_pgtune recipe #20
Open
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
This recipe contains fine-tuning to make sure that postgresql is configured the correct way on the node is being deployed to (in terms of memory usage, for instance). (cherry picked from commit acf6a53)
There are a couple of fixes that we want from https://github.com/sous-chefs/postgresql/blob/master/recipes/config_pgtune.rb (cherry picked from commit bc7292280dccd5e89721ec0869fc69662cff096f)
Now that we enable the config_pgtune recipe, the max_connection settings must live there. This mostly reverts 251a5de. (cherry picked from commit 42d14f66336caf0b0d88541f919da3fcef054790)
|
LGTM - we should test it and merge it |
Open
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.
Closes #9
I need to update the commit messages (the commits are cherry-picked, but no commits went upstream yet)