Fix add_pgnode.yml: Clear the data directory for the new node for bootstrapping #527
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.
This Pull Request introduces an important update to the conditions used for clearing the PostgreSQL data and custom WAL directories in our Ansible deployment scripts. The adjustment ensures that the directories are properly prepared not only for master nodes but also for replica nodes, specifically addressing scenarios where pgbackrest is used or when deploying new nodes.
Changes
postgresql_data_dir
) and the custom WAL directory (postgresql_wal_dir
).patroni_cluster_bootstrap_method
does not usepgbackrest
.pgbackrest
is not part of thepatroni_create_replica_methods
, or it is a new node (indicated by thenew_node
variable).Note: When performing PITR, we do not clear the directory if pgbackrest is used to be able to use the '--delta' restore option.
Fixed: