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

Clarify requirement for local/remote pgBackRest versions to match.

Browse Source
This commit is contained in:
Greg Clough
2025-02-15 18:00:00 +00:00
committed by GitHub
parent 47f050f8fd
commit 82299eb4cd
3 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/xml/release/2025/2.55.0.xml
View File

@@ -126,6 +126,17 @@
<release-doc-list>
<release-improvement-list>
<release-item>
<github-pull-request id="2541"/>
<release-item-contributor-list>
<release-item-contributor id="greg.clough"/>
<release-item-reviewer id="david.steele"/>
</release-item-contributor-list>
<p>Clarify requirement for local/remote <backrest/> versions to match.</p>
</release-item>
<release-item>
<github-pull-request id="2538"/>

5
doc/xml/release/contributor.xml
View File

@@ -403,6 +403,11 @@
<contributor-id type="github">gmustdie</contributor-id>
</contributor>
<contributor id="greg.clough">
<contributor-name-display>Greg Clough</contributor-name-display>
<contributor-id type="github">gclough</contributor-id>
</contributor>
<contributor id="greg.sabino.mullane">
<contributor-name-display>Greg Sabino Mullane</contributor-name-display>
<contributor-id type="github">turnstep</contributor-id>

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

@@ -983,6 +983,8 @@
<title>Upgrading {[project]} from v2.x to v2.y</title>
<p>Upgrading from <proper>v2.x</proper> to <proper>v2.y</proper> is straight-forward. The repository format has not changed, so for most installations it is simply a matter of installing binaries for the new version. It is also possible to downgrade if you have not used new features that are unsupported by the older version.</p>
<admonition type="important">The local and remote <backrest/> versions must match exactly so they should be upgraded together. If there is a mismatch, WAL archiving and backups will not function until the versions match. In such a case, the following error will be reported: <id>[ProtocolError] expected value '2.x' for greeting key 'version' but got '2.y'</id>.</admonition>
</section>
</section>