Re: Assistance Needed: Issue with pg_upgrade and --link option

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Pradeep Kumar <spradeepkumar29(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Assistance Needed: Issue with pg_upgrade and --link option
Date: 2023-06-28 10:46:58
Message-ID: 33a1bd9927f8849c8d4c4718eae060e78341eba8.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2023-06-28 at 15:40 +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>
>
> 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

That looks fine. The files exist only once, and the 41MB that only exist in
the new data directory are catalog data and other stuff that is different
on the new cluster.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-06-28 10:53:38 Re: [PoC] pg_upgrade: allow to upgrade publisher node
Previous Message Pradeep Kumar 2023-06-28 10:19:44 Re: Assistance Needed: Issue with pg_upgrade and --link option