Repository navigation
Turn on summarize_wal when SUMMARIZE_WAL=on (PG17+) - #74
Draft
souravbiswassanto wants to merge 1 commit into
Draft
souravbiswassanto wants to merge 1 commit into
souravbiswassanto wants to merge 1 commit into
Conversation
Incremental pg_basebackup needs WAL summaries reaching back to the parent backup. Standbys write them too, so a promoted standby can carry on the incremental chain. Signed-off-by: souravbiswassanto <saurov@appscode.com>
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
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.
Writes
summarize_wal = onintopostgresql.confwhenSUMMARIZE_WAL=on, in the primary and standby scripts for PostgreSQL 17 and 18.Incremental
pg_basebackupneeds WAL summaries reaching back to the parent backup. Standbys summarize the WAL they replay too, so after a failover the new primary can continue the incremental chain.The operator sets the env for archived databases on 17.11+ / 18.6+ (kubedb/postgres#960). Without the env nothing changes.
Verified on k3s:
summarize_walwas on in all three pods (primary and both standbys), and an incremental backup taken right after a failover succeeded.