Re: pg_upgrade parallelism - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: pg_upgrade parallelism
Date
Msg-id 5cbe532ce8c27f0c00006f5e986d2066f8fe60f9.camel@vmware.com
Whole thread Raw
In response to Re: pg_upgrade parallelism  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg_upgrade parallelism
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Sequence's value can be rollback after a crashed recovery.
Next
From: Tom Lane
Date:
Subject: Re: Sequence's value can be rollback after a crashed recovery.