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 1tuXYp-009dgX-Bg for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Mar 2025 14:04:51 +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 1tuXYm-00FSdC-Lv for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Mar 2025 14:04:48 +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.94.2) (envelope-from ) id 1tuXYm-00FSbA-Br for pgsql-hackers@lists.postgresql.org; Tue, 18 Mar 2025 14:04:48 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tuXYk-003WCw-07 for pgsql-hackers@postgresql.org; Tue, 18 Mar 2025 14:04:47 +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 52IE4fP8017821; Tue, 18 Mar 2025 10:04:41 -0400 From: Tom Lane To: Robert Haas cc: Nathan Bossart , Greg Sabino Mullane , pgsql-hackers@postgresql.org, bruce@momjian.us Subject: Re: optimize file transfer in pg_upgrade In-reply-to: References: Comments: In-reply-to Robert Haas message dated "Tue, 18 Mar 2025 09:40:52 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17819.1742306681.1@sss.pgh.pa.us> Date: Tue, 18 Mar 2025 10:04:41 -0400 Message-ID: <17820.1742306681@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > I'm not quite sure what the best thing is to do is for the pg_upgrade > tests in particular, and it may well be best to do as you propose for > now and figure that out later. But I question whether just rerunning > all of those tests with several different mode flags is the right > thing to do. Why for example does 005_char_signedness.pl need to be > checked under both --link and --clone? I would guess that there are > one or maybe two tests in src/bin/pg_upgrade/t that needs to test > --link and --clone and they should grow internal loops to do that > (when supported by the local platform) and PG_UPGRADE_TEST_MODE should > go in the garbage. +1 I'd be particularly allergic to running 002_pg_upgrade.pl multiple times, as that's one of our most expensive tests, and I flat out don't believe that expending that many cycles could be justified. Surely we can test these modes sufficiently in some much cheaper and more targeted way. regards, tom lane