Update wal_level guide #610
Open
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
According to the PG docs, 'archive' and 'hot_standby' both redirect to 'replica': https://www.postgresql.org/docs/16/runtime-config-wal.html#GUC-WAL-LEVEL
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.
According to the PG docs, 'archive' and 'hot_standby' both redirect to 'replica': https://www.postgresql.org/docs/16/runtime-config-wal.html#GUC-WAL-LEVEL
About this change - What it does
It's confusing for users because those values are no longer valid. It also gives the impression that these values must be changed before running pghoard, but in fact, the default Postgres value (replica) for wal_level is sufficient.
Why this way
The values
archiveandhot_standbyare outdated