fix: create pg_wal if missing before single-user mode#19
Merged
Conversation
Snapshots from Windows PostgreSQL installs (EDB/BigSQL layout) may not include pg_wal if it lives outside the snapshotted directory. Creating an empty pg_wal allows postgres --single to start and complete crash recovery; it will initialise a new WAL segment on its own.
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
1 participant
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.
Snapshots from Windows PostgreSQL installs (EDB/BigSQL layout) do not include
pg_walif it lives outside the snapshotted directory. This causedsetup-authto fail immediately with:The fix creates an empty
pg_walbefore invokingpostgres --singleif it's absent. Postgres will initialise a fresh WAL segment inside it and proceed with crash recovery normally.Observed on
tamanu-replica-palau-devandtamanu-replica-palau-prod(PG 12, Windows source host).