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 1tuwHa-00EhG8-1N for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Mar 2025 16:28:42 +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 1tuwHY-007YU3-9p for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Mar 2025 16:28:40 +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 1tuwHX-007YTq-Vh for pgsql-hackers@lists.postgresql.org; Wed, 19 Mar 2025 16:28:39 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tuwHU-003n6h-1W for pgsql-hackers@postgresql.org; Wed, 19 Mar 2025 16:28:39 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 52JGSXFo712606; Wed, 19 Mar 2025 12:28:33 -0400 From: Tom Lane To: Nathan Bossart cc: Andres Freund , Robert Haas , Greg Sabino Mullane , pgsql-hackers@postgresql.org, bruce@momjian.us Subject: Re: optimize file transfer in pg_upgrade In-reply-to: References: <17820.1742306681@sss.pgh.pa.us> <7rhxl5nl5cuenm4kzprjhaojo74m2teuwzjffcrdi6bxx6b2wn@orb5h3mteh2y> Comments: In-reply-to Nathan Bossart message dated "Wed, 19 Mar 2025 10:31:22 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <712604.1742401713.1@sss.pgh.pa.us> Date: Wed, 19 Mar 2025 12:28:33 -0400 Message-ID: <712605.1742401713@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > I'm currently planning to commit this sometime early-ish next week. One > notable loose end is the lack of a pg_upgrade test with a non-default > tablespace, but that is an existing problem that IMHO is best handled > separately (since we can only test it in cross-version upgrades). Agreed that that shouldn't block this, but we need some kind of plan for testing it better. regards, tom lane