From: | Alex Balashov <abalashov(at)evaristesys(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Differential backup in database migration |
Date: | 2022-02-16 12:36:48 |
Message-ID: | A98302EE-531C-4E12-998F-E81AC3ABC847@evaristesys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Huh! I suppose I don’t know; I just assumed it would take a bunch of fragile, error-prone upgrade jumps across major releases to get five major releases forward.
I’ll definitely follow up on your suggestion, as it is by far the simplest!
> On Feb 16, 2022, at 7:08 AM, Paul Smith <paul(at)pscs(dot)co(dot)uk> wrote:
>
> On 16/02/2022 11:24, Alex Balashov wrote:
>> 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,
>
> How do you know it will not be binary compatible?
>
> I'm fairly sure I've upgraded 9.5 to 14 using pg_upgrade... If you use the 'link' option in pg_upgrade it just takes a few minutes with databases that big.
>
> I'd take a backup, put it on a test machine with 9.5 and try to upgrade it. You may be pleasantly surprised
>
>
> Paul
>
>
> --
>
>
> Paul Smith Computer Services
> Tel: 01484 855800
> Vat No: GB 685 6987 53
>
> Sign up for news & updates at http://www.pscs.co.uk/go/subscribe
>
>
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2022-02-16 13:42:28 | Re: Differential backup in database migration |
Previous Message | Paul Smith | 2022-02-16 12:08:14 | Re: Differential backup in database migration |