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 1pWgUt-0001yY-Rl for pgsql-general@arkaria.postgresql.org; Mon, 27 Feb 2023 16:37:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pWgUs-0006qP-4J for pgsql-general@arkaria.postgresql.org; Mon, 27 Feb 2023 16:37:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWgUr-0006qG-QJ for pgsql-general@lists.postgresql.org; Mon, 27 Feb 2023 16:37:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pWgUo-0002j8-Ro for pgsql-general@lists.postgresql.org; Mon, 27 Feb 2023 16:37:05 +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 31RGawdP372206; Mon, 27 Feb 2023 11:36:58 -0500 From: Tom Lane To: Adrian Klaver cc: =?UTF-8?Q?D=c3=a1vid_Suchan?= , pgsql-general@lists.postgresql.org Subject: Re: pg_upgradecluster transfering only a portion of the data In-reply-to: References: Comments: In-reply-to Adrian Klaver message dated "Mon, 27 Feb 2023 08:14:25 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <372204.1677515818.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 27 Feb 2023 11:36:58 -0500 Message-ID: <372205.1677515818@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > On 2/27/23 07:44, Dávid Suchan wrote: >> After a successful prompt finished, I checked the database and the size >> went from originally 20gb (in 9.6) to 700~ mb (in 14) while the disk >> space available shrank by about 2gb meaning that there is still the 20gb >> of data. I tried the entire process twice (since I had created an AWS > 1) How did you measure the size of the database clusters? If it was based on something like "du", perhaps the measurement was fooled by the fact that most of the data files will be hard-linked between the old and new clusters. regards, tom lane