public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Jatinder Singh Sandhu <[email protected]>
To: [email protected]
Subject: Re: physical replication compatibilty
Date: Wed, 15 Apr 2026 15:16:54 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAB25yESoKwnZfVGpW6y5kg0bd-psZvCeivY2zGb7C7037fK2dg@mail.gmail.com>
References: <CAB25yESoKwnZfVGpW6y5kg0bd-psZvCeivY2zGb7C7037fK2dg@mail.gmail.com>



On 4/15/26 3:06 PM, Jatinder Singh Sandhu wrote:
> Dear PostgreSQL Community,
> I am currently planning a major version upgrade from PostgreSQL 16 to 
> PostgreSQL 17. I have three node patroni cluster. While I am aware that 
> logical replication is the standard approach for cross-version 
> migrations, I am curious about the feasibility of physical streaming 
> replication in this specific scenario.
> Specifically, I would like to clarify:
> 
>  1. Is physical streaming replication backward compatible between these
>     two major versions?
>  2. Since many data files remain consistent between versions, is there
>     any supported method to leverage physical block-level replication to
>     minimize the initial data synchronization time before a cutover?
> 
> I understand that WAL formats and system catalogs typically change 
> between major releases, but I wanted to confirm if there are any modern 
> workarounds or "late-binding" techniques available in the v17 ecosystem.
> Thank you for your time and expertise.

I think you are looking for:

https://www.postgresql.org/docs/17/pgupgrade.html

In particular this:

13. Upgrade streaming replication and log-shipping standby servers

Whether that will play well with the Patroni cluster or not is not 
something I can comment on.

It is covered below though:

https://patroni.readthedocs.io/en/latest/existing_data.html#major-upgrade-of-postgresql-version

> Best regards,

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: physical replication compatibilty
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox