MIME-Version: 1.0
References: <CAJCZko+aaFkt8C+oXQFZYBUCD4f_gkAroaE1ZQemtdqNr+W=xQ@mail.gmail.com>
 <CAJ9xe=sLOZQ26JF==dNwmhh0LSkLgwMhsxXAH2e1J1CqkyHaBw@mail.gmail.com>
 <1e16e035-e7e5-460a-86f8-9a207fd2ffef@aklaver.com> <CAJ9xe=v3QX-Q4vmKYfos_UG75BD9j_Q_ekAu5G501o+Niy6fkA@mail.gmail.com>
 <56a90390-5a4b-4ffc-a0bc-5a09c46d6876@aklaver.com>
In-Reply-To: <56a90390-5a4b-4ffc-a0bc-5a09c46d6876@aklaver.com>
From: Asad Ali <asadalinagri@gmail.com>
Date: Sat, 26 Oct 2024 23:38:18 +0500
Message-ID: <CAJ9xe=sjaOOe8MdgD379U7Z=PuR3EOouvwW8obdXuOcS4au7pA@mail.gmail.com>
Subject: Re: Pgsql 16 to 14 using builtin logical
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Durgamahesh Manne <maheshpostgres9@gmail.com>, 
	pgsql-general <pgsql-general@lists.postgresql.org>, 
	PostgreSQL mailing lists <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000c524250625658a07"
Archived-At: <https://www.postgresql.org/message-id/CAJ9xe%3DsjaOOe8MdgD379U7Z%3DPuR3EOouvwW8obdXuOcS4au7pA%40mail.gmail.com>
Precedence: bulk

--000000000000c524250625658a07
Content-Type: text/plain; charset="UTF-8"

I missed to mentioned in the last.

On Sat, Oct 26, 2024, 10:51 PM Adrian Klaver <adrian.klaver@aklaver.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.klaver@aklaver.com
>
>

--000000000000c524250625658a07
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I missed to mentioned in the last.</div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 26, 2024, 1=
0:51 PM Adrian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adri=
an.klaver@aklaver.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">On 10/26/24 10:06, Asad Ali wrote:<br>
&gt; <br>
&gt; In the typical upgrade scenario, replication flows from the lower <br>
&gt; (older) version to the higher (newer) version. Here, the source is the=
 <br>
&gt; older version (e.g., PostgreSQL 14), and the target is the newer versi=
on <br>
&gt; (e.g., PostgreSQL 16).<br>
<br>
So how does that fit with your statement?:<br>
<br>
&quot;PostgreSQL&#39;s built-in logical replication allows for replicating =
data <br>
between different versions of PostgreSQL, provided the source version is <b=
r>
higher than or equal to the target version.&quot;<br>
<br>
&gt; <br>
&gt; Replicating from a higher version (PostgreSQL 16) to a lower one <br>
&gt; (PostgreSQL 14) is possible but unconventional and not usually done fo=
r <br>
&gt; upgrades.<br>
&gt; <br>
&gt; <br>
&gt; Best Regards,<br>
&gt; Asad Ali<br>
&gt; <br>
<br>
-- <br>
Adrian Klaver<br>
<a href=3D"mailto:adrian.klaver@aklaver.com" target=3D"_blank" rel=3D"noref=
errer">adrian.klaver@aklaver.com</a><br>
<br>
</blockquote></div>

--000000000000c524250625658a07--