From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_upgradecluster transfering only a portion of the data |
Date: | 2023-02-27 16:46:52 |
Message-ID: | 1488b8f2-fe98-3be2-0d27-4c52734f15af@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/27/23 08:36, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> 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.
Does that happen without the --link option?
>
> regards, tom lane
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-02-27 16:48:49 | Re: pg_upgradecluster transfering only a portion of the data |
Previous Message | Tom Lane | 2023-02-27 16:36:58 | Re: pg_upgradecluster transfering only a portion of the data |