Message-ID: <c947af51d2ea8bc12985450fb7cfdb6d9679b578.camel@cybertec.at>
Subject: Re: [PATCH] Doc: clarify that pg_upgrade statistics transfer works
 cross-version
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bruce Momjian <bruce@momjian.us>
Cc: Nikolay Samokhvalov <nik@postgres.ai>, pgsql-docs@lists.postgresql.org
Date: Wed, 25 Mar 2026 07:03:01 +0100
In-Reply-To: <acLT6tXlMxgQRsT6@momjian.us>
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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/c947af51d2ea8bc12985450fb7cfdb6d9679b578.camel%40cybertec.at>
Precedence: bulk

On Tue, 2026-03-24 at 14:11 -0400, Bruce Momjian wrote:
> On Tue, Mar 24, 2026 at 05:53:27PM +0100, Laurenz Albe wrote:
> > Bruce, you are confusing me.  Your first sentence suggests that you
> > (erroneously) thought that upgrading statistics only works when upgradi=
ng
>=20
> Right.
>=20
> > *from* v18 or better.  But your last sentence suggests that you'd rathe=
r
> > not add anything to the documentation that could dispel that misconcept=
ion.
>=20
> So, we don't normally document cases where a limitation does not exist.=
=20
> I think the logical place to document this is in the PG 18 release
> notes.  I am still confused why people, like myself, got this wrong.=20
> What is the source of the confusion?  Just unclear release notes?

I understand now, thanks.  I agree with you in principle, but I wouldn't
see that as a hard rule that should stand in the way of clarity.

Let me quote a precedent from https://www.postgresql.org/docs/current/upgra=
ding.html

  Minor releases never change the internal storage format and are always
  compatible with earlier and later minor releases of the same major
  version number. For example, version 10.1 is compatible with version 10.0
  and version 10.6.

To me, that clarifies that there is no limitation to performing minor
updates with a simple restart.  I think that is useful information.

Perhaps you'd feel better if we phrase it as a limitation:

  Transferring optimizer statistics only work when upgrading to PostgreSQL
  version v18 or later, but there is no such limitation to the version of
  the old cluster.

I like my original suggestion better, though.

Yours,
Laurenz Albe