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.
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.
