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.94.2) (envelope-from ) id 1u7vQs-009rWB-Lx for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Apr 2025 12:11:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u7vQq-00GlPY-SK for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Apr 2025 12:11:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u7vQq-00GlPQ-Ig for pgsql-hackers@lists.postgresql.org; Thu, 24 Apr 2025 12:11:57 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u7vQo-001mBe-0D for pgsql-hackers@lists.postgresql.org; Thu, 24 Apr 2025 12:11:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=Content-Type:MIME-Version:Message-ID:Subject:To:From:Date: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: In-Reply-To:References; bh=xWDm23mmgJ1ATt2rdI1CEf5ZspJgBp52mSa8dDX6ZkY=; b=lA gW9w3vp6y6kXMr+CKRLahLQqVTMLgMMeAwVWKBeJbcgmBEGfYaOFI7+dSux4PotBxv5mSZyK8PeOG Q+0Y4lZyMKWBDQhqLeam0R9pfLzi2ygttJkXl+QsRBc1uHC8tobaL5qP7Wxk8JK4d06Q8RQGe6s+f +rFJjzPPMWDEBM/f822vdH7T2F1Ble/plhEVqa8D9Q5BVQhagbb+giiNO+rgFOs+YC/UCN/XhTjEF 35bs1rwbEhl2fR2tRyn3nehpqjKpQfkTMg71J4r9bCBQ/nuE5YpC8e6RCcxFAH0YB/UoPt4P4kxh6 JlxPaWxMdnMIVM9I15qaI8UAkCn28siQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1u7vQm-008oZP-24 for pgsql-hackers@lists.postgresql.org; Thu, 24 Apr 2025 08:11:52 -0400 Date: Thu, 24 Apr 2025 08:11:52 -0400 From: Bruce Momjian To: PostgreSQL-development Subject: pg_upgrade-breaking release Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Do we think most people are _not_ going to use pg_upgrade now that we are defaulting to checksums being enabled by default in PG 18? And if so, do we think we are ever going to have a storage-format-changing release where pg_upgrade cannot be used? Maybe it is too late to ask this, but I am asking anyway. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.