Re: Pgsql 16 to 14 using builtin logical

From: Asad Ali <asadalinagri(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pgsql 16 to 14 using builtin logical
Date: 2024-10-26 18:38:18
Message-ID: CAJ9xe=sjaOOe8MdgD379U7Z=PuR3EOouvwW8obdXuOcS4au7pA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I missed to mentioned in the last.

On Sat, Oct 26, 2024, 10:51 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 10/26/24 10:06, Asad Ali wrote:
> >
> > In the typical upgrade scenario, replication flows from the lower
> > (older) version to the higher (newer) version. Here, the source is the
> > older version (e.g., PostgreSQL 14), and the target is the newer version
> > (e.g., PostgreSQL 16).
>
> So how does that fit with your statement?:
>
> "PostgreSQL's built-in logical replication allows for replicating data
> between different versions of PostgreSQL, provided the source version is
> higher than or equal to the target version."
>
> >
> > Replicating from a higher version (PostgreSQL 16) to a lower one
> > (PostgreSQL 14) is possible but unconventional and not usually done for
> > upgrades.
> >
> >
> > Best Regards,
> > Asad Ali
> >
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2024-10-26 21:15:56 Re: Pgsql 16 to 14 using builtin logical
Previous Message Adrian Klaver 2024-10-26 17:51:21 Re: Pgsql 16 to 14 using builtin logical