db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-02-15 14:03:26 +02:00
Code Issues Releases Activity

Clarify archive-push multi-repo behavior.

Browse Source 
Clarify that archive-push will not be able to push ahead in other repositories if one is failing unless archive-async in enabled.
This commit is contained in:
David Steele 2024-07-18 11:19:25 +07:00 committed by GitHub
parent c85191e024
commit ec3e387bb7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/xml/release/2024/2.53.xml
View File

@ -105,4 +105,19 @@
</release-item>
</release-improvement-list>
</release-core-list>
<release-doc-list>
<release-improvement-list>
<release-item>
<github-pull-request id="2398"/>
<release-item-contributor-list>
<release-item-contributor id="david.steele"/>
<release-item-reviewer id="stefan.fercot"/>
</release-item-contributor-list>
<p>Clarify <cmd>archive-push</cmd> multi-repo behavior.</p>
</release-item>
</release-improvement-list>
</release-doc-list>
</release>

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

@ -2395,7 +2395,9 @@
<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>
<p>The <cmd>archive-push</cmd> 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.</p>
<p>The <cmd>archive-push</cmd> command will always push WAL to the archive in all configured repositories. When a repository cannot be reached, WAL will still be pushed to other repositories. However, for this to work effectively, <br-setting>archive-aync=y</br-setting> must be enabled; otherwise, the other repositories can only get one WAL segment ahead of the unreachable repository. Also, note that if WAL cannot be pushed to any repository, then <postgres/> will not remove it from the <path>pg_wal</path> directory, which may cause the volume to run out of space.</p>
<p>Backups 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.</p>
</section>
<!-- ======================================================================================================================= -->