Re: Assistance Needed: Issue with pg_upgrade and --link option
От | Laurenz Albe |
---|---|
Тема | Re: Assistance Needed: Issue with pg_upgrade and --link option |
Дата | |
Msg-id | 33a1bd9927f8849c8d4c4718eae060e78341eba8.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: Assistance Needed: Issue with pg_upgrade and --link option (Pradeep Kumar <spradeepkumar29@gmail.com>) |
Ответы |
Re: Assistance Needed: Issue with pg_upgrade and --link option
|
Список | 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
В списке pgsql-hackers по дате отправления: