Re: pg_upgrade parallelism

From: Jacob Champion <pchampion(at)vmware(dot)com>
To: "pryzby(at)telsasoft(dot)com" <pryzby(at)telsasoft(dot)com>
Cc: "jcasanov(at)systemguards(dot)com(dot)ec" <jcasanov(at)systemguards(dot)com(dot)ec>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade parallelism
Date: 2021-11-23 21:37:34
Message-ID: 5cbe532ce8c27f0c00006f5e986d2066f8fe60f9.camel@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2021-11-23 at 13:51 -0600, Justin Pryzby wrote:
>
> I guess you're concerned for someone who wants to be able to run pg_upgrade and
> preserve the ability to start the old cluster in addition to the new.

Right. What I'm worried about is, if disk space or write performance on
the new cluster is a concern, then having a copy-mode upgrade silently
use copy-on-write could be a problem if the DBA needs copy mode to
actually copy.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-11-23 21:41:06 Re: Sequence's value can be rollback after a crashed recovery.
Previous Message Tom Lane 2021-11-23 21:12:17 Re: Sequence's value can be rollback after a crashed recovery.