Date: Fri, 24 Sep 2021 09:39:35 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: "Westwood, Giles" <g.westwood@orcid.org>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Performance for initial copy when using pg_logical to upgrade
 Postgres
Message-ID: <20210924143934.GN831@telsasoft.com>
References: 
 <CAEMahfP0FCUUuFrDY7gpacwSRp_jM7eNCA__kbVeMupWShE=8A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAEMahfP0FCUUuFrDY7gpacwSRp_jM7eNCA__kbVeMupWShE=8A@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20210924143934.GN831%40telsasoft.com>
Precedence: bulk

On Fri, Sep 24, 2021 at 03:28:50PM +0100, Westwood, Giles wrote:
> At Orcid we're trying to upgrade our Postgres database (10 to 13) using
> pg_logical for no downtime. The problem we have is how long the initial
> copy is taking for the ~500GB database. If it takes say 20days to complete,
> will we need to have 20days of WAL files to start catching up when it's
> complete?

Did you see this thread and its suggestions to 1) set bulk load parameters;
and, 2) drop indexes and FKs ?

https://www.postgresql.org/message-id/flat/4A8EFC4E-A264-457D-A8E7-AE324ED9ABD4@thebuild.com

-- 
Justin