Updated Postgres Best Practices for Replication Slots #276
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
…d the max_slot_wal_keep_size section to Managing & Monitoring Replication Lag
michaelbarnes
changed the title
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.
This PR introduces the following changes to the Production Readiness Best Practices Guide, specifically the Postgres DB specific best practices:
max_slot_wal_keep_sizesection has been renamed toManaging & Monitoring Replication Lag. Which I think reads better and gets the point across. The introduction sentence was also restructured in response to the section name change.Managing Replication Slots. This section focuses on how developers can inspect replication slots and suggests configuring theidle_replication_slot_timeoutconfiguration parameter to make the management of replication slots easier.