Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w5Qyi-003FON-0q for pgsql-docs@arkaria.postgresql.org; Wed, 25 Mar 2026 16:21:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w5Qyg-00F5bn-16 for pgsql-docs@arkaria.postgresql.org; Wed, 25 Mar 2026 16:21:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w5Qyg-00F5bf-0D for pgsql-docs@lists.postgresql.org; Wed, 25 Mar 2026 16:21:06 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w5Qyb-00000000zlq-3Ny0 for pgsql-docs@lists.postgresql.org; Wed, 25 Mar 2026 16:21:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=lzy1cNseZHPONTm8o1L2cVpAcIxpDESN92UemvYVNW4=; b=KG+VA HI1OjviRogOl/Bukqs5EZ3emwVfH5GNXruOYLZUb83mO0kdyEeiOMjsztVV9jztwaMzNgciZHDNqW 5Tmk8oSI6e9ZLrLKe1avtyDfUoqExtEnoYcuQQQusuMKX+MNBv9fqopzTGxfrt1SB7Rufr0TWxElz 09X0+Ukvsz5vUW0jopYZFi54EL6Mk6B9Bih/ZaDy+AQglPRvH9s/wz1P+JFHgwUUtluaIdYQEerct fQPp84/P0omO2phMtTQ9aeKi2sXjL988SeM1R7sWasoHQ4cSOe5M4CVLCECVFxxfB+1retK8qXAZ5 h9JqksEo5KZSLHWpp68Zwszs9Fd0A==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w5Qya-0000000B9lr-0rz3; Wed, 25 Mar 2026 12:21:00 -0400 Date: Wed, 25 Mar 2026 12:21:00 -0400 From: Bruce Momjian To: Laurenz Albe Cc: Nikolay Samokhvalov , pgsql-docs@lists.postgresql.org Subject: Re: [PATCH] Doc: clarify that pg_upgrade statistics transfer works cross-version Message-ID: References: <1a7d3c03e6169e6340f9d77667433fd0cc5f5897.camel@cybertec.at> <48ad7007c0bbca725847473fe410cdda5753c65d.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Mar 25, 2026 at 07:03:01AM +0100, Laurenz Albe wrote: > 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 upgrading > > > > Right. > > > > > *from* v18 or better. But your last sentence suggests that you'd rather > > > not add anything to the documentation that could dispel that misconception. > > > > So, we don't normally document cases where a limitation does not exist. > > 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. > > 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/upgrading.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. Right. > 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. Uh, we added the feature in PG 18, so why would we say it only works in PG 18 --- that is kind of obvious. I am still asking, why did people, like me, think it only worked for _old_ PG 18 servers. If we find where that was communicated, we can clarify it _there_. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.