Add async/poll support for long-running pg_basebackup operations #1
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.
pg_basebackupfor large databases can take hours, hitting Ansible's default 120s timeout during replica cloning.Changes
pg_basebackup_timeout(default: 14400s / 4 hours) inroles/postgres/replica/final/defaults/main.ymlpg_basebackuptask to useasync/poll: 0with separateasync_statuswait loop(timeout / 10) | intwith minimum of 1, polls every 10 secondsrc != 0 or 'error' in stderrlogic, adds safety checks for undefined variablesUsage
Override timeout in
config.ymlfor very large databases:Pattern follows existing
roles/barman/first_backup/tasks/backup.ymlimplementation.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.