Postgres Pro
Downloads
Home   >   mailing lists

Re: V12 to V16 Upgrade -- does size matters? - Mailing list pgsql-admin

From Ron Johnson
Subject Re: V12 to V16 Upgrade -- does size matters?
Date
Msg-id CANzqJaDjFKzYoJd+F3z16nSo8tw4XZfETcrsMDB2ZDefuZ503g@mail.gmail.com
Whole thread Raw
In response to V12 to V16 Upgrade -- does size matters?  (Edwin UY <edwin.uy@gmail.com>)
List pgsql-admin
Tree view
On Mon, Feb 24, 2025 at 11:48 PM Edwin UY <edwin.uy@gmail.com> wrote:
Hi,

Does size matter when doing the upgrade?
Just noted the non-PROD database is 20G and the PROD one is around 500G.
Does the size of the database affect how long the upgrade will finish?

Yes, if you run standard pg_upgrade. (It's got to copy all the files to the new directory.)
No, if you run pg_upgrade with the --link or  --clone options.

520GB isn't that much, though.

Beware, though: using the --link and --clone options don't let you revert after starting the new instance.

Especially when running the ANALYZE post-upgrade.

Maybe, or maybe not.  Bigger tables take longer to ANALYZE.  But if there are lots of CPUs and you've got lots of medium-sized tables, then --jobs=$(nproc) will chew through them much faster.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Edwin UY
Date:
Subject: V12 to V16 Upgrade -- does size matters?
Next
From: shammat@gmx.net
Date:
Subject: Re: Changing the Datatype from Bit to Boolean.