MIME-Version: 1.0
In-Reply-To: 
 <CAM527d9Qev=xKQHmp-9rMhhn65zw0g6hsJz-HHgLkbaScvqwDQ@mail.gmail.com>
References: 
 <CAM527d_Qt9ZGt99vgTaidfObRiDH0R5F_uEfum9zHeZbc+LwCQ@mail.gmail.com>
 <1a7d3c03e6169e6340f9d77667433fd0cc5f5897.camel@cybertec.at>
 <CAM527d89GmcMV5GD2PXS-a3ay3YE-HVSwV4NT0_o2ySf_5v8Kw@mail.gmail.com>
 <acKoBql5eQWpQH4N@momjian.us>
 <48ad7007c0bbca725847473fe410cdda5753c65d.camel@cybertec.at>
 <acLT6tXlMxgQRsT6@momjian.us>
 <c947af51d2ea8bc12985450fb7cfdb6d9679b578.camel@cybertec.at>
 <acQLbAQntxQzfhtP@momjian.us>
 <CAM527d9Qev=xKQHmp-9rMhhn65zw0g6hsJz-HHgLkbaScvqwDQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 25 Mar 2026 19:33:42 -0700
Message-ID: 
 <CAKFQuwYmspFfkno8Xf_RL4C5AQFDgvSXRcg5kmofrRy=cz88jw@mail.gmail.com>
Subject: Re: [PATCH] Doc: clarify that pg_upgrade statistics transfer works
 cross-version
To: Nikolay Samokhvalov <nik@postgres.ai>
Cc: Bruce Momjian <bruce@momjian.us>, Laurenz Albe <laurenz.albe@cybertec.at>,
	"pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000893429064de43672"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwYmspFfkno8Xf_RL4C5AQFDgvSXRcg5kmofrRy%3Dcz88jw%40mail.gmail.com>
Precedence: bulk

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

On Wednesday, March 25, 2026, Nikolay Samokhvalov <nik@postgres.ai> wrote:

>
> If you don't know anything about implementation, it is natural to
> expect that something new will work only when both old and new
> clusters support it.
>
>
But we don=E2=80=99t call out =E2=80=9Cnew features=E2=80=9D in the documen=
tation.  Just
=E2=80=9Cfeatures=E2=80=9D.  And so when the pg_upgrade docs says =E2=80=9C=
pg_upgrade supports
upgrades from 9.2.X and later=E2=80=9D then unless there is a note to the c=
ontrary
(which there is not here) that applies to everything pg_upgrade does.

Put differently, read the docs as if you were unaware in which version that
capability was introduced.  This is the style/assumption the documentation
is written in/using.

David J.

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

On Wednesday, March 25, 2026, Nikolay Samokhvalov &lt;<a href=3D"mailto:nik=
@postgres.ai">nik@postgres.ai</a>&gt; wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><br>
If you don&#39;t know anything about implementation, it is natural to<br>
expect that something new will work only when both old and new<br>
clusters support it.<br>
<br>
</blockquote><div><br></div><div>But we don=E2=80=99t call out =E2=80=9Cnew=
 features=E2=80=9D in the documentation.=C2=A0 Just =E2=80=9Cfeatures=E2=80=
=9D.=C2=A0 And so when the pg_upgrade docs says =E2=80=9Cpg_upgrade support=
s upgrades from 9.2.X and later=E2=80=9D then unless there is a note to the=
 contrary (which there is not here) that applies to everything pg_upgrade d=
oes.</div><div><br></div><div>Put differently, read the docs as if you were=
 unaware in which version that capability was introduced.=C2=A0 This is the=
 style/assumption the documentation is written in/using.</div><div><br></di=
v><div>David J.</div><div><br></div>

--000000000000893429064de43672--