Re: Assistance Needed: Issue with pg_upgrade and --link option - Mailing list pgsql-hackers

From Pradeep Kumar
Subject Re: Assistance Needed: Issue with pg_upgrade and --link option
Date
Msg-id CAJ4xhP=7MyWBxW5w6qZws=YGa1NuhS9iNmJWk7aSxBxXqC-vig@mail.gmail.com
Whole thread Raw
In response to Re: Assistance Needed: Issue with pg_upgrade and --link option  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Assistance Needed: Issue with pg_upgrade and --link option
List pgsql-hackers
Sure,
du -sk ~/pradeep_test/pg_upgrade_testing/postgres_11.4/master ~/pradeep_test/pg_upgrade_testing/postgres_14/new_pg
11224524 /home/test/pradeep_test/pg_upgrade_testing/postgres_11.4/master
41952 /home/test/pradeep_test/pg_upgrade_testing/postgres_14/new_pg

On Wed, Jun 28, 2023 at 11:54 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Wed, 2023-06-28 at 11:49 +0530, Pradeep Kumar wrote:
> I was under the impression that the --link option would create hard links between the
> old and new cluster's data files, but it appears that the entire old cluster data was
> copied to the new cluster, resulting in a significant increase in the new cluster's size.

Please provide some numbers, ideally

  du -sk <old_data_directory> <new_data_directory>

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Show WAL write and fsync stats in pg_stat_io
Next
From: Pradeep Kumar
Date:
Subject: Re: Assistance Needed: Issue with pg_upgrade and --link option