Re: pg_upgradecluster transfering only a portion of the data

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: 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:14:25
Message-ID: fd0d1b0d-3017-5d6c-cc95-18fd664c35ad@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/27/23 07:44, Dávid Suchan wrote:
> Hello, I tried upgrading pg db from version 9.6 to 14 by using
> pg_upgradecluster command. I freshly installed pg 14 -> ran
> pg_dropcluster 14 main --stop -> and then upgraded using
> pg_upgradecluster 9.6 main.
> 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?

2) pg_upgrade will not remove the old cluster automatically so it not
surprising the overall disk usage increased.

3) Did you see any messages at end of upgrade mentioning issues?

4) Have you connected to new cluster to see if everything is there?

5) Does the Postgres log provide any relevant information?

> EC2 snapshot for this) and the result was the same.
> Is my solution to migrating old pg version to the new one wrong? Before
> this I tried the same process with around 300mb of data and all of that
> transferred successfully. If I did not understand the pg_upgradecluster
> command, what would be the best practice when upgrading pg version with
> huge amounts of data(could be a terabyte)?

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-02-27 16:36:58 Re: pg_upgradecluster transfering only a portion of the data
Previous Message Tom Lane 2023-02-27 16:12:19 Re: ERROR: unsupported Unicode escape sequence - in JSON-type column