On 28.06.23 12:46, Laurenz Albe wrote:
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,
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
This is my numbers.
df ~/pradeep_test/pg_upgrade_testing/postgres_11.4/master
~/pradeep_test/pg_upgrade_testing/postgres_14/new_pg
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/nvme0n1p4_crypt 375161856 102253040 270335920 28% /home
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
On 28.06.23 08:24, Laurenz Albe 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,
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
Dear Postgres Hackers,
I hope this email finds you well. I am currently facing an issue while
performing an upgrade using the pg_upgrade utility with the --link option.
I was under the impression that the --link option would create hard links
between the old and new cluster's data files, but it
