From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Differential backup in database migration
Date: Wed, 16 Feb 2022 14:42:28 +0100
Message-ID: <c80ce4a7-2c4f-9c08-e926-27418c6aa058@gmx.net> (raw)
In-Reply-To: <F804329E-8A76-42F8-BCD0-A32FE6FA243D@evaristesys.com>
References: <F804329E-8A76-42F8-BCD0-A32FE6FA243D@evaristesys.com>
Alex Balashov schrieb am 16.02.2022 um 12:24:
> I’m faced with the daunting prospect of upgrading a PG 9.6
> installation to 14, in the process migrating a ~400 GB database. Due
> to the large jump in major versions, the on-disk block storage of
> course will not be in the slightest bit binary-compatible, so I will
> have to dump out the DB & import it into the target DB, live via a
> network pipe.
pg_upgrade will happily do the migration from 9.6 directly to 14
If the length of the downtime is a concern, the --link option will make this quite fast.
Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Differential backup in database migration
In-Reply-To: <c80ce4a7-2c4f-9c08-e926-27418c6aa058@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox