Skip to content

Clarify WAL archive restoration during pg_rewind --dry-run in v5.6 #466

Open

Description

@Hanabi9248

The English and Chinese v5.6 tool references say that pg_rewind --dry-run leaves the target directory unchanged. An operator can therefore expect a preview to leave the target untouched even when --restore-target-wal is specified. If the WAL scan needs a segment missing from the target, that combination can still restore a file into the target’s pg_wal directory. English reference Chinese reference

The release loads the target cluster’s restore_command when --restore-target-wal is enabled. The WAL scan passes that setting to the archive restore helper when a required local segment cannot be opened. This scan runs in dry-run mode too. The helper uses the target pg_wal directory as the destination for the restore. Option handling WAL scan Restore destination

Update both --dry-run entries to describe which rewind changes are skipped and explicitly document the possible archive restore when --restore-target-wal is used.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions