| From: | Pradeep Kumar <spradeepkumar29(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Assistance Needed: Issue with pg_upgrade and --link option |
| Date: | 2023-06-28 10:10:37 |
| Message-ID: | CAJ4xhP=7MyWBxW5w6qZws=YGa1NuhS9iNmJWk7aSxBxXqC-vig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)albe(at)cybertec(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pradeep Kumar | 2023-06-28 10:19:44 | Re: Assistance Needed: Issue with pg_upgrade and --link option |
| Previous Message | Nazir Bilal Yavuz | 2023-06-28 10:09:14 | Show WAL write and fsync stats in pg_stat_io |