From: | kasem adel <kasemadel8(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Advice Needed: Simultaneous Upgrade of Two-Node PostgreSQL 11 Cluster |
Date: | 2025-01-06 23:59:10 |
Message-ID: | CAP-pBm-Y=b6YxHPag0TLertO=7OCo1kN8RVjBg5mvJNx6Y56KA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Dear Laurenz Albe
Our application for reporting is dependent on the replica node for
handling read-only operations. If we proceed with the proposed changes, it
would result in a one-month application downtime, which would significantly
impact our operations and is not a feasible option for us.
We would greatly appreciate your insights and support in identifying
alternative solutions to minimize down time (one month)or another solution
alternative for rebuild replica from scratch. Your expertise and advice
would be invaluable in helping us navigate this challenge effectively.
Thank you for your time and assistance.
في الاثنين، ٦ يناير ٢٠٢٥ ٧:١٣ م Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> كتب:
> On Sun, 2025-01-05 at 19:57 +0200, kasem adel wrote:
> > Proposed Upgrade Approach:
> >
> > Simultaneous Upgrade Process:
> >
> > Install new PostgreSQL version packages on both nodes
> > Run pg_upgrade with --check flag on both nodes
> > Execute pg_upgrade with --link option on both nodes simultaneously
> > Update Patroni configuration for new version on both nodes
>
> No, that won't work.
>
> You have to upgrade the primary, then rebuild the standby with
> "patronictl reinit". There is no safe way to upgrade the standby.
>
> Yours,
> Laurenz Albe
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-01-07 06:57:19 | Re: Advice Needed: Simultaneous Upgrade of Two-Node PostgreSQL 11 Cluster |
Previous Message | Guillaume Lelarge | 2025-01-06 20:34:27 | Re: Postgresql 17 incremental backup |