| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgradecluster transfering only a portion of the data |
| Date: | 2023-02-27 16:56:21 |
| Message-ID: | 12a7a897-ff85-5280-7721-5e6d0e7cb30b@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/27/23 08:48, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> On 2/27/23 08:36, Tom Lane wrote:
>>> If it was based on something like "du", perhaps the measurement
>>> was fooled by the fact that most of the data files will be hard-linked
>>> between the old and new clusters.
>
>> Does that happen without the --link option?
>
> No, but the OP didn't mention whether he used that, and even if he
> didn't say it explicitly the pg_upgradecluster wrapper might've
> supplied it.
Alright the OP's command was:
pg_upgradecluster 9.6 main
pg_upgradecluster needs the --link(-k) option to use link instead of copy.
>
> regards, tom lane
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-02-27 16:58:34 | Re: pg_upgradecluster transfering only a portion of the data |
| Previous Message | Tom Lane | 2023-02-27 16:48:49 | Re: pg_upgradecluster transfering only a portion of the data |