From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Karthik Krishnakumar <karthikk(at)zohocorp(dot)com>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Upgrading postgres quickly, without downtime. |
Date: | 2023-02-17 13:00:48 |
Message-ID: | 6225428d-ed25-051e-3991-44d330786649@sqlexec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
pg_upgrade --link is the way to go for sure, but pay attention to the
details surrounding it for primary and replicas.
Regards,
Michael Vitale
Laurenz Albe wrote on 2/17/2023 7:13 AM:
> On Fri, 2023-02-17 at 15:01 +0530, Karthik Krishnakumar wrote:
>> I have a number of pg servers(~100 (each with a couple of replicas, so 300
>> clusters in total), each with ~2TB data) that is running version 10.
>> I am planning on upgrading to PG 15 and looking for ways to get it done
>> without downtime and quickly.
>> There seem to be a couple of ways to do this -
>> 1. dump/restore or upgrade -> but this causes downtime.
>> 2. logical replication/pglogical -> this is going to be slow, adds additional
>> load on the master, and it isnt recommended to do DDL during time.
>>
>> I do have daily backups of these databases.
>> Is there a way I can use these daily backups to upgrade to 15 and sync the changes for the day alone?
>> I can code in C/scripts, and know bit of internals and wanted to ask where to start on this.
>> I am also open to any alternate ideas.
> Take 10 minutes downtime and use "pg_upgrade --link".
>
> Yours,
> Laurenz Albe
>
>
Regards,
Michael Vitale
Michaeldba(at)sqlexec(dot)com <mailto:michaelvitale(at)sqlexec(dot)com>
703-600-9343
From | Date | Subject | |
---|---|---|---|
Next Message | Nikhil Ingale | 2023-02-17 15:59:14 | Redirect RAISE NOTICE and errors to separate log file |
Previous Message | Laurenz Albe | 2023-02-17 12:13:32 | Re: Upgrading postgres quickly, without downtime. |