Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4kFX-0021e6-Kr for pgsql-general@arkaria.postgresql.org; Sat, 26 Oct 2024 17:06:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t4kFV-00AL5I-VP for pgsql-general@arkaria.postgresql.org; Sat, 26 Oct 2024 17:06:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4kFV-00AL59-KK for pgsql-general@lists.postgresql.org; Sat, 26 Oct 2024 17:06:49 +0000 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t4kFT-0037cW-Px for pgsql-general@lists.postgresql.org; Sat, 26 Oct 2024 17:06:49 +0000 Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-5cb6ca2a776so3952793a12.0 for ; Sat, 26 Oct 2024 10:06:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729962406; x=1730567206; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=SeHfcBpXmZ+gs3oShDFdWbPx0yEwNvn4IsxpBfsd3wA=; b=htqs+Jlx0Wz65LCAg/0G0GxTdpzrKvhnqh9k4WipRRD3JqQduYZ0iXnGSY+n5QDrsw Dj/devArae1SR21DFQM8ja7Wi29z256TmEcqAgSaOVhj5bwwTj6FLW2qdLFwepqKBFjM mVkFGdwvz7HVzS3jJw6X67LkxLvL4o7NJtbczWGVUBLopKv6CYv5IumEyOZipQbJmWaf 5IsSdUW/9E/PjQzfrle4y9dWrmtyJ2E89E0qHdC+vqbp1PhpMiPRFQvS9/6JoBIjvCg0 A8/ndBV7t58+fUiD0WmV6srT1hxY7kqqRzzBGa1kyiaFH92H4zr4ZctgzvnJ1lM2IXc9 jKTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729962406; x=1730567206; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SeHfcBpXmZ+gs3oShDFdWbPx0yEwNvn4IsxpBfsd3wA=; b=R9vIxxykyV2UGgkhspUk9oDJ+xXXa0V1HBFne79BLCkOUxWrYp5/XDecLnzG9IsLxZ elmXSl/hawCHFGqpPwDaYzSCZI00c0VxI5YNK9e3T2nQFbhLH+k2Ncw7GQt671LrjvBp meAv/5dL8g6H5aPxgspWO6irPoyRz3qu8AJhy9VPQ5qZxni/m42CbURD4ZYWIOvvQ/Id KIKXmgiaj9MGLxy1Yrr822NJN71RQyGTexn1ZODtoTeHNanFcSsvW0qZrh107F4yDlwx mK84+yRBixuwlTDaOKMQEPse0hDCg2oiXikOIFJN40VQ+NvmpOd+MKyGFoJs0N64vrea f6Gw== X-Forwarded-Encrypted: i=1; AJvYcCXy7AVtlWWBCswuZ+/e+eCAcgmDw1s572cddbTPwpphZ7S/W8id/oCsrPss44W2uEAmJxMMqE0tGcSGARrk@lists.postgresql.org X-Gm-Message-State: AOJu0YzzcQGr11IP38uGunfISImny8QzYJ2/yhmHW91BTRtS3qcHcroF 5ZnX4aTreIiyiYaHO6Yw1pQIRd5H9CFdR6ZWFAUlDd9u0TTlGs34Rg/+kM+4P1ukueJ+DcwIJ4i vuieHQwCIk+MwfhlWsMFmYSy6LSM= X-Google-Smtp-Source: AGHT+IG5hh0SR7KkM+4rGh4caBFH7OQrnsVznbdwKJeGeWej96GUW1vk4Pzz12zszVnlzX3s089T4Y2AwW3LUtrnG8k= X-Received: by 2002:a05:6402:249d:b0:5cb:6718:7326 with SMTP id 4fb4d7f45d1cf-5cbbf8caef6mr2397171a12.21.1729962405408; Sat, 26 Oct 2024 10:06:45 -0700 (PDT) MIME-Version: 1.0 References: <1e16e035-e7e5-460a-86f8-9a207fd2ffef@aklaver.com> In-Reply-To: <1e16e035-e7e5-460a-86f8-9a207fd2ffef@aklaver.com> From: Asad Ali Date: Sat, 26 Oct 2024 22:06:33 +0500 Message-ID: Subject: Re: Pgsql 16 to 14 using builtin logical To: Adrian Klaver Cc: Durgamahesh Manne , pgsql-general , PostgreSQL mailing lists Content-Type: multipart/alternative; boundary="000000000000a6382006256442e8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a6382006256442e8 Content-Type: text/plain; charset="UTF-8" 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). 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 On Sat, Oct 26, 2024, 9:10 PM Adrian Klaver wrote: > On 10/25/24 23:02, Asad Ali wrote: > > Hi Durgamahesh, > > > > Yes, you can replicate a PostgreSQL 16 database to PostgreSQL 14 using > > built-in logical replication. 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. > > I am not following or maybe it's just your idea of what is the source > and what is the target. In the common case of upgrading a database to a > newer version the logical replication would be from the lower source to > the higher target. > > > > > > Regards, > > Asad > > > > > > On Sat, Oct 26, 2024, 8:28 AM Durgamahesh Manne > > > wrote: > > > > Hi > > > > Can we replicate 16 to 14 using builtin logical similarly pglogical? > > > > Regards > > Durga Mahesh > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --000000000000a6382006256442e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

In the typi= cal upgrade scenario, replication flows from the lower (older) version to t= he higher (newer) version. Here, the source is the older version (e.g., Pos= tgreSQL 14), and the target is the newer version (e.g., PostgreSQL 16).
=

Replicating from a high= er version (PostgreSQL 16) to a lower one (PostgreSQL 14) is possible but u= nconventional and not usually done for upgrades.

Best Regards,
Asad Ali

On Sat, Oct 26, 2024, 9:10 PM Adrian Klaver &= lt;adrian.klaver@aklaver.com> wrote:
On 10/25/24 23:02, As= ad Ali wrote:
> Hi Durgamahesh,
>
> Yes, you can replicate a PostgreSQL 16 database to PostgreSQL 14 using=
> built-in logical replication. PostgreSQL's built-in logical replic= ation
> allows for replicating data between different versions of PostgreSQL, =
> provided the source version is higher than or equal to the target vers= ion.

I am not following or maybe it's just your idea of what is the source <= br> and what is the target. In the common case of upgrading a database to a newer version the logical replication would be from the lower source to the higher target.


>
> Regards,
> Asad
>
>
> On Sat, Oct 26, 2024, 8:28 AM Durgamahesh Manne
> <maheshpostgres9@gmail.com <mailto:maheshpostg= res9@gmail.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi
>
>=C2=A0 =C2=A0 =C2=A0Can we replicate 16 to 14 using builtin logical sim= ilarly pglogical?
>
>=C2=A0 =C2=A0 =C2=A0Regards
>=C2=A0 =C2=A0 =C2=A0Durga Mahesh
>

--
Adrian Klaver
adrian.klaver@aklaver.com

--000000000000a6382006256442e8--