Re: pg_upgrade 13.6 to 15.1?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pf(at)pfortin(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade 13.6 to 15.1?
Date: 2023-01-15 21:07:12
Message-ID: 1694534.1673816832@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> --clone

I think --clone is probably contraindicated here, given that Pierre
already made a copy of the data. If I understand how that works,
it'll just wind up making another whole copy, but in a time-extended
manner as the tables are modified. Over the long run there would
still be two copies of the DB on the new disk, which doesn't seem
like what he wants.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message pf 2023-01-15 21:27:50 Re: pg_upgrade 13.6 to 15.1?
Previous Message Adrian Klaver 2023-01-15 21:00:58 Re: pg_upgrade 13.6 to 15.1?