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
Implement Node Label Functionality for pgdump Restores (#585)
* Implemented node label functionality for pgdump restores. Also,
refactored node label validation, and corrected a defect in which
and node label with an empty value was considered valid.
* Make pgbasebackup the default for the "pgo backup" command
Copy file name to clipboardExpand all lines: hugo/content/Design/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -176,7 +176,7 @@ on PG 9.6/9.5 systems, the command you will use is *select pg_xlog_replay_resume
176
176
* there is currently no Operator validation of user entered pgBackRest command options, you will need to make sure to enter these correctly, if not the pgBackRest restore command can fail.
177
177
* the restore workflow does not perform a backup after the restore nor does it verify that any replicas are in a working status after the restore, it is possible you might have to take actions on the replica to get them back to replicating with the new restored primary.
178
178
* pgbackrest.org suggests running a pgbackrest backup after a restore, this needs to be done by the DBA as part of a restore
179
-
* when performing a restore, the **node-label**option can be utilized to target a specific node for both the pgBackRest restore job and the new (i.e. restored) primary deployment that is then created for the cluster. If a node label is not specified, the restore job will not target any specific node, and the restored primary deployment will inherit any node label's defined for the original primary deployment.
179
+
* when performing a pgBackRest restore, the **node-label**flag can be utilized to target a specific node for both the pgBackRest restore job and the new (i.e. restored) primary deployment that is then created for the cluster. If a node label is not specified, the restore job will not target any specific node, and the restored primary deployment will inherit any node label's defined for the original primary deployment.
0 commit comments