You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: The annotation skipEmptyWalArchiveCheck is not working when recovering a Cluster via Barman Cloud Plugin #457
The skipEmptyWalArchiveCheck annotation is supported and intended to bypass the safety check that prevents overwriting existing data in a shared WAL archive bucket during recovery with the Barman Cloud Plugin, but this is strongly discouraged unless you are highly familiar with PostgreSQL recovery, as misuse can cause severe data loss [docs].
Currently, there is a confirmed bug where this annotation does not work as expected during cluster recovery with the Barman Cloud Plugin, causing the cluster to fail with an error about expecting an empty archive even when the annotation is set. This issue is tracked and addressed in an open pull request in the cloudnative-pg repository, but the fix has not yet been merged as of the latest update [PR #8216].
Some users have reported temporary workarounds, such as commenting out the plugin configuration or ensuring the plugin is enabled as WALArchiver, but these may not be suitable for all scenarios and should be used with caution [issue].
Keep an eye on the status of the PR and plan to upgrade once the fix is released. Use the annotation only if you fully understand the risks involved.
Activity
fix: check for empty WAL archive during WAL archiving
dosubot commentedon Aug 4, 2025
The skipEmptyWalArchiveCheck annotation is supported and intended to bypass the safety check that prevents overwriting existing data in a shared WAL archive bucket during recovery with the Barman Cloud Plugin, but this is strongly discouraged unless you are highly familiar with PostgreSQL recovery, as misuse can cause severe data loss [docs].
Currently, there is a confirmed bug where this annotation does not work as expected during cluster recovery with the Barman Cloud Plugin, causing the cluster to fail with an error about expecting an empty archive even when the annotation is set. This issue is tracked and addressed in an open pull request in the cloudnative-pg repository, but the fix has not yet been merged as of the latest update [PR #8216].
Some users have reported temporary workarounds, such as commenting out the plugin configuration or ensuring the plugin is enabled as WALArchiver, but these may not be suitable for all scenarios and should be used with caution [issue].
Keep an eye on the status of the PR and plan to upgrade once the fix is released. Use the annotation only if you fully understand the risks involved.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
fix: check for empty WAL archive during WAL archiving
fix: check for empty WAL archive during WAL archiving (#458)
feat(container): update image ghcr.io/cloudnative-pg/charts/plugin-ba…
chore(deps): update dependency https://github.com/cloudnative-pg/plug…