Skip to content

Conversation

@Agalin
Copy link
Collaborator

@Agalin Agalin commented May 27, 2025

All other basic operations already support custom flags. Even the restore itself is supposed to already support them but, as opposed to Barman, pgBackRest has two separate commands used during the restore:

  • restore (responsible for downloading and applying the main backup),
  • archive-get (responsible for PITR part - retrieving necessary WAL files later than the backup itself).

Currently only the archive-get part is customizable.

Especially painful is the inability to configure parallelism as that means the main backup can take very long time to download, hence a dedicated field for it (just like for backups).

All other basic operations already support custom flags.
Even the restore itself is supposed to already support them but, as opposed to Barman, pgBackRest has two separate commands used during the restore:
* restore (responsible for downloading and applying the main backup),
* archive-get (responsible for PITR part - retrieving necessary WAL files later than the backup itself).

Currently only the archive-get part is customizable.

Especially painful is the inability to configure parallelism as that means the main backup can take very long time to download, hence a dedicated field for it (just like for backups).

Signed-off-by: Szymon Soloch <[email protected]>
@psliwka psliwka self-assigned this May 27, 2025
@Agalin Agalin marked this pull request as ready for review May 28, 2025 08:16
@Agalin Agalin merged commit 0b8491d into main May 28, 2025
1 check passed
@Agalin Agalin deleted the agalin/restore-flags branch May 28, 2025 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants