From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pf(at)pfortin(dot)com |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_upgrade 13.6 to 15.1? |
Date: | 2023-01-15 20:59:20 |
Message-ID: | 1693377.1673816360@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
pf(at)pfortin(dot)com writes:
> On Sun, 15 Jan 2023 14:47:35 -0500 Tom Lane wrote:
>> I think you misunderstand how this is supposed to work. The -D
>> argument should point at an *empty* data directory that has been
>> freshly initialized with the new version's initdb. pg_upgrade then
>> transfers data into that from the old database (-d argument).
> I was hoping to avoid the hours worth of copying to the NVMe SSD.
> The instructions refer to upgrading with --link; would that save the copy
> time?
Yes, but to use --link you must have both data directories on the
same filesystem, so this is still the wrong thing.
Try something like
mv /mnt/work/var/lib/pgsql/data /mnt/work/var/lib/pgsql/data13
initdb /mnt/work/var/lib/pgsql/data
pg_upgrade ... -d /mnt/work/var/lib/pgsql/data13 -D /mnt/work/var/lib/pgsql/data --link ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-01-15 21:00:58 | Re: pg_upgrade 13.6 to 15.1? |
Previous Message | pf | 2023-01-15 20:41:39 | Re: pg_upgrade 13.6 to 15.1? |