db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-09-16 09:06:18 +02:00
Code Issues Releases Activity

Fix incorrect reference to stanza-update in the user guide.

Browse Source 
This should be stanza-upgrade. Also fix in the git history cache since the comment was copied from the user guide.
This commit is contained in:
Abubakar Mohammed
2022-03-24 15:59:41 -06:00
committed by David Steele
parent 14016a86e7
commit 3dd7960451
3 changed files with 16 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/resource/git-history.cache
View File

@@ -3060,7 +3060,7 @@
"commit": "1dbb3bf50b94dcc9d53dfe1e5ad57a17bd6d38e8",
"date": "2021-03-08 13:31:13 -0500",
"subject": "Multiple repository support.",
"body": "Up to four repositories may be configured. A potential benefit is the ability to have a local repository for fast restores and a remote repository for redundancy.\r\n\r\nSome commands, e.g. stanza-create/stanza-update, will automatically work with all configured repositories while others, e.g. stanza-delete, will require a repository to be specified using the repo option. See the command reference for details on which commands require the repository to be specified.\r\n\r\nNote that the repo option is not required when only repo1 is configured in order to maintain backward compatibility. However, the repo option is required when a single repo is configured as, e.g. repo2. This is to prevent command breakage if a new repository is added later.\r\n\r\nThe archive-push command will always push WAL to the archive in all configured repositories but backups will need to be scheduled individually for each repository. In many cases this is desirable since backup types and retention will vary by repository. Likewise, restores must specify a repository. It is generally better to specify a repository for restores that has low latency/cost even if that means more recovery time. Only restore testing can determine which repository will be most efficient.\r\nFor single repository configurations there should be no change in behavior."
"body": "Up to four repositories may be configured. A potential benefit is the ability to have a local repository for fast restores and a remote repository for redundancy.\r\n\r\nSome commands, e.g. stanza-create/stanza-upgrade, will automatically work with all configured repositories while others, e.g. stanza-delete, will require a repository to be specified using the repo option. See the command reference for details on which commands require the repository to be specified.\r\n\r\nNote that the repo option is not required when only repo1 is configured in order to maintain backward compatibility. However, the repo option is required when a single repo is configured as, e.g. repo2. This is to prevent command breakage if a new repository is added later.\r\n\r\nThe archive-push command will always push WAL to the archive in all configured repositories but backups will need to be scheduled individually for each repository. In many cases this is desirable since backup types and retention will vary by repository. Likewise, restores must specify a repository. It is generally better to specify a repository for restores that has low latency/cost even if that means more recovery time. Only restore testing can determine which repository will be most efficient.\r\nFor single repository configurations there should be no change in behavior."
},
{
"commit": "8b87e66448a30b07c12ac00cb2c6ee2f5f29f043",

14
doc/xml/release.xml
View File

@@ -120,6 +120,15 @@
<release-doc-list>
<release-bug-list>
<release-item>
<release-item-contributor-list>
<release-item-contributor id="abubakar.mohammed"/>
<release-item-reviewer id="david.steele"/>
</release-item-contributor-list>
<p>Fix incorrect reference to <id>stanza-update</id> in the user guide.</p>
</release-item>
<release-item>
<release-item-contributor-list>
<release-item-contributor id="david.steele"/>
@@ -10806,6 +10815,11 @@
</contributor>
<!-- The order of other contributors is alpha by name -->
<contributor id="abubakar.mohammed">
<contributor-name-display>Abubakar Mohammed</contributor-name-display>
<contributor-id type="github">abubakarm94</contributor-id>
</contributor>
<contributor id="adam.brusselback">
<contributor-name-display>Adam Brusselback</contributor-name-display>
<contributor-id type="github">Tostino</contributor-id>

2
doc/xml/user-guide.xml
View File

@@ -2148,7 +2148,7 @@
<p>Multiple repositories may be configured as demonstrated in <link section="/s3-support">S3 Support</link>. A potential benefit is the ability to have a local repository for fast restores and a remote repository for redundancy.</p>
<p>Some commands, e.g. <cmd>stanza-create</cmd>/<cmd>stanza-update</cmd>, will automatically work with all configured repositories while others, e.g. <link section="/delete-stanza">stanza-delete</link>, will require a repository to be specified using the <br-option>repo</br-option> option. See the <link url="command.html">command reference</link> for details on which commands require the repository to be specified.</p>
<p>Some commands, e.g. <cmd>stanza-create</cmd>/<cmd>stanza-upgrade</cmd>, will automatically work with all configured repositories while others, e.g. <link section="/delete-stanza">stanza-delete</link>, will require a repository to be specified using the <br-option>repo</br-option> option. See the <link url="command.html">command reference</link> for details on which commands require the repository to be specified.</p>
<p>Note that the <br-option>repo</br-option> option is not required when only <br-option>repo1</br-option> is configured in order to maintain backward compatibility. However, the <br-option>repo</br-option> option <i>is</i> required when a single repo is configured as, e.g. <br-option>repo2</br-option>. This is to prevent command breakage if a new repository is added later.</p>