MIME-Version: 1.0
In-Reply-To: 
 <CALVdoE7PbL_NRqc9R1M6Hnefe54FVow4s1DLd-j1BmjpBz=LiQ@mail.gmail.com>
References: <176704110285.978869.17442362272602441829@wrigleys.postgresql.org>
 <CAKFQuwa15OzTjrv5WE+K1BsHipHP1QSosSG=uQvgdq6SVW1JsQ@mail.gmail.com>
 <CALVdoE7PbL_NRqc9R1M6Hnefe54FVow4s1DLd-j1BmjpBz=LiQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Mon, 19 Jan 2026 11:23:25 -0700
Message-ID: 
 <CAKFQuwaaYM2VL0mwQ34iEK8yxMJZ0LpQ5X3chn46Xci9_6mBtQ@mail.gmail.com>
Subject: Re: clarification for pg_basebackup and major versions
To: Alexey Shishkin <alexey.shishkin@enterprisedb.com>
Cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000007897d30648c1c903"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwaaYM2VL0mwQ34iEK8yxMJZ0LpQ5X3chn46Xci9_6mBtQ%40mail.gmail.com>
Precedence: bulk

--0000000000007897d30648c1c903
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Monday, January 19, 2026, Alexey Shishkin <
alexey.shishkin@enterprisedb.com> wrote:

> Hi, Team !
>
> Some more clarification about pg_basebackup which should be available in
> the documentation:
>
> - if pg_basebackup works between different versions of the same OS (ex.
> RHEL8 and RHEL9)
> - if pg_basebackup works between different types of OS Linux (ex. RHEL10
> and Debian13) or OS Windows (ex. Windows 2016 and Windows 2019)
> - if pg_basebackup works between different types of OS (ex. Ubuntu 24.04
> and Windows 2022)
> - if pg_basebackup works between different platforms (ex. Linux on amd64
> and Linux on arm64)
> - if pg_basebackup works between 32-bit OS and 64-bit OS
>
>>
>>
Please don=E2=80=99t top-post.

I agree this these dynamics aren=E2=80=99t readily exposed in the documenta=
tion.  I
disagree that pg_basebackup should be considered as an authoritative
location for covering the material.  It would simply link to such a
location in notes or =E2=80=9Csee also=E2=80=9D.

In short, though, it like pretty much any client program will function
correctly regardless of differences with the server.  But a physical backup
is only truly promised to work if the environment that is processing the
data matches the environment that produced the data.

David J.

--0000000000007897d30648c1c903
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Monday, January 19, 2026, Alexey Shishkin &lt;<a href=3D"mailto:alexey.s=
hishkin@enterprisedb.com">alexey.shishkin@enterprisedb.com</a>&gt; wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Hi, Team !</div><div=
><br></div><div>Some more clarification about pg_basebackup which should be=
 available in the documentation:</div><div><br></div><div>- if pg_basebacku=
p works between different versions of the same OS (ex. RHEL8 and RHEL9)</di=
v><div>- if pg_basebackup works between different types of OS Linux (ex. RH=
EL10 and Debian13) or OS Windows (ex. Windows 2016 and Windows 2019)</div><=
div>- if pg_basebackup works between different types of OS (ex. Ubuntu 24.0=
4 and Windows 2022)</div><div>- if pg_basebackup works between different pl=
atforms (ex. Linux on amd64 and Linux on arm64)</div><div>- if pg_basebacku=
p works between 32-bit OS and 64-bit OS</div></div><div class=3D"gmail_quot=
e"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div></block=
quote></div></blockquote><div><br></div><div>Please don=E2=80=99t top-post.=
</div><div><br></div><div>I agree this these dynamics aren=E2=80=99t readil=
y exposed in the documentation.=C2=A0 I disagree that pg_basebackup should =
be considered as an authoritative location for covering the material.=C2=A0=
 It would simply link to such a location in notes or =E2=80=9Csee also=E2=
=80=9D.</div><div><br></div><div>In short, though, it like pretty much any =
client program will function correctly regardless of differences with the s=
erver.=C2=A0 But a physical backup is only truly promised to work if the en=
vironment that is processing the data matches the environment that produced=
 the data.</div><div><br></div><div>David J.</div>

--0000000000007897d30648c1c903--