Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHADn-0000v0-NJ for pgsql-general@arkaria.postgresql.org; Sun, 15 Jan 2023 21:07:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pHADm-0005Xc-BZ for pgsql-general@arkaria.postgresql.org; Sun, 15 Jan 2023 21:07:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHADm-0005XA-1Y for pgsql-general@lists.postgresql.org; Sun, 15 Jan 2023 21:07:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pHADj-0007ne-Sl for pgsql-general@lists.postgresql.org; Sun, 15 Jan 2023 21:07:17 +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 30FL7CxA1694535; Sun, 15 Jan 2023 16:07:12 -0500 From: Tom Lane To: Adrian Klaver cc: pf@pfortin.com, pgsql-general@lists.postgresql.org Subject: Re: pg_upgrade 13.6 to 15.1? In-reply-to: <0276c684-7091-08c0-5854-0899111a0b19@aklaver.com> References: <20230115142732.0ec38e2a.pfortin@pfortin.com> <9a8899f2-211f-ae2a-1071-c1567d7ae988@aklaver.com> <20230115154139.5a60b4dd@pfortin.com> <0276c684-7091-08c0-5854-0899111a0b19@aklaver.com> Comments: In-reply-to Adrian Klaver message dated "Sun, 15 Jan 2023 13:00:58 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1694533.1673816832.1@sss.pgh.pa.us> Date: Sun, 15 Jan 2023 16:07:12 -0500 Message-ID: <1694534.1673816832@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > --clone I think --clone is probably contraindicated here, given that Pierre already made a copy of the data. If I understand how that works, it'll just wind up making another whole copy, but in a time-extended manner as the tables are modified. Over the long run there would still be two copies of the DB on the new disk, which doesn't seem like what he wants. regards, tom lane