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 1w56ER-002tQv-1B for pgsql-docs@arkaria.postgresql.org; Tue, 24 Mar 2026 18:11:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w56EP-008My4-29 for pgsql-docs@arkaria.postgresql.org; Tue, 24 Mar 2026 18:11:58 +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 1w56EP-008Mxw-1S for pgsql-docs@lists.postgresql.org; Tue, 24 Mar 2026 18:11:57 +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 1w56EO-00000000pbY-0Zle for pgsql-docs@lists.postgresql.org; Tue, 24 Mar 2026 18:11:56 +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=Pq/Pk8/wdibpX4AirnvrojjFfzF1jP9cmK7P0VnoA1k=; b=MILHl eUmbSzQJm4jVcetMgrIxj0F3q6uJ2pNFLT3esF+7wlCX6HVwvO8Tqofd5tTbvrcPWLQuHVSGN6Zxo iAKx4aTf90AniWYIPWQTxQEMfgFHWIZ1webabeVnd5dXjnLWLf9vC3HWJhz35W+xRxs7sdmRxK3M6 MKWKle6orycxSudWohvGbGpmyRQjRlv6P01ZcNn1NNLSX5S2DCcYturRPvg+A0r6r08fYPG+T2osY mkye2ziR7LNHDYW6TeHKXVz4lY35cA7Wpb0v7bahhlFdPfzjwQH41pFWtOCWT0yg0DSPF6W1FWmMK qCgpD37DgyXjRudkOCsCZz3w4pFaA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1w56EM-00000003qGq-3Pe7; Tue, 24 Mar 2026 14:11:54 -0400 Date: Tue, 24 Mar 2026 14:11:54 -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: <48ad7007c0bbca725847473fe410cdda5753c65d.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Mar 24, 2026 at 05:53:27PM +0100, Laurenz Albe wrote: > On Tue, 2026-03-24 at 11:04 -0400, Bruce Momjian wrote: > > On Tue, Mar 24, 2026 at 05:36:42AM -0700, Nikolay Samokhvalov wrote: > > > On Mon, Mar 23, 2026 at 23:59 Laurenz Albe wrote: > > > How about adding a simple remark, like > > I was under the same impression --- that it only worked with upgrades > > _from_ PG 18 and later. However, I can't find any documentation on this > > limitation, so why did so many think this was true? I don't think > > adding anything to the docs is the right approach. > > 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? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.