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 1sVEWP-008jNa-PX for pgsql-sql@arkaria.postgresql.org; Sat, 20 Jul 2024 18:09:29 +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 1sVEWN-000uLW-MV for pgsql-sql@arkaria.postgresql.org; Sat, 20 Jul 2024 18:09:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sVEWN-000uLN-7x for pgsql-sql@lists.postgresql.org; Sat, 20 Jul 2024 18:09:27 +0000 Received: from mail-vs1-xe34.google.com ([2607:f8b0:4864:20::e34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sVEWK-000ZRU-U7 for pgsql-sql@lists.postgresql.org; Sat, 20 Jul 2024 18:09:26 +0000 Received: by mail-vs1-xe34.google.com with SMTP id ada2fe7eead31-48febcc8819so985652137.3 for ; Sat, 20 Jul 2024 11:09:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721498964; x=1722103764; 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=t6s9fExv1Xwj/Y+tBep/56ifrpqi9KTT+17E7lwpOzc=; b=bM2c9L/quQm7NYrZ0lZVktLi4/sq2/B3qA2L6jlzfi0X4ioR+N6d/jEdogUi+UIqR2 DDYIrg75CIE5PLusjdDLp7NoMPiVs9y65egmWshyokNsNUeIb2jKYF73DJDfEquiounT hGRjqR/Egda42WLh4qO7UZcQMzL0qrRy7JuiT8jSbKTwxDdFwoAleGKZ7AkD9IghDAp6 KLpPPqCJ018BfPfzMMzgMFSN5w6l2g5X62zyYE/2lifCWGoSBCl6pU3XTvvRabiYffXL 8Wk3R28x+PPZClGcE1lv3gTdvVE63cjHQ0ajaot8SmQnjh9WX6jEPLinEouafI+es8cO ewFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721498964; x=1722103764; 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=t6s9fExv1Xwj/Y+tBep/56ifrpqi9KTT+17E7lwpOzc=; b=paVMs363D0ula6aL2J98EcdZZkBbJu3ovebLvOg+PfXtaGMKAicgd7/sxkefjFkBLq trTbCATPLyISDlDqfvHd7R3XJOMh1mi+laHyejfl5SUyp5YoFGD9oAzTNQx28S3Nw7Mn VppR6dKa409GpkOm2oXPiXGUx4Yz5wixCNZxG+1laf+82HBaeuuygMOxScJgGXcfzdQ9 aHynDFvv6gX7/8wkVD1Z42V2tt2vIznosejoaxL0Ihg6vHzO66Lw5HE6jmHo3QftJQkn YSqMo6HDMo2tf72Wk8gkXDMGdBdRPyGyJxIZq/H7MeOBodYUUnM9amsdSBoiHiztGcjx Kbdw== X-Gm-Message-State: AOJu0YxkeR0Wy2v9P6UfOTNGsPNmyfcosDMm/7DxPY+NKgw4yhVClnU2 vBQVXL1F6GSkE5iqnYkvPMlAHHhM4Xie48nusb4T2KuohfwmE9WtJF/Yx7+7YzRsfyY5eQVYBID VU9YkuD+alJup9DsHJjyvo6dOzVOIFglqjbg= X-Google-Smtp-Source: AGHT+IFr8CgZ827VrsFjExyB0OglIE1wm1jLIkk3oXLs3jDKbhOkLrn0r28SuFOi91US8xhMzkLuKNO3paV7ESvdrIA= X-Received: by 2002:a05:6102:8022:b0:48d:7692:51ba with SMTP id ada2fe7eead31-4928b936037mr2965069137.4.1721498963972; Sat, 20 Jul 2024 11:09:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Sat, 20 Jul 2024 23:09:15 +0500 Message-ID: Subject: Re: Using replication to upgrade db from 12 to 16 To: Frank Komsic Cc: "pgsql-sql@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000003a97a9061db1b6fa" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003a97a9061db1b6fa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Frank On Sat, Jul 20, 2024 at 11:00=E2=80=AFPM Frank Komsic wrote: > Hi Zashif, > > > > I read somewhere that it was possible to have a replication on an Upgrade= d > major version I believe by using logical replication? > The restrictions I mentioned are with Physical Replication. You can use Logical Replication which doesn't have these restrictions but it has some of its own e.g. 1. It supports replication of Tables only 2. It support only DML Commands (INSERT, UPDATE, DELETE) and TRUNCATE (with some restrictions) You can check the restrictions on following link https://www.postgresql.org/docs/current/logical-replication-restrictions.ht= ml Regards Kashif Zeeshan > > > Not sure myself, but was hoping there is a way as our application require= d > some debugging after the upgrade due to improper concatenation of SQL > statements that was not enforced in PGSQL-12. > > > > Thanks > > Frank > > > > *From: *Kashif Zeeshan > *Date: *Saturday, July 20, 2024 at 1:45=E2=80=AFPM > *To: *Frank Komsic > *Cc: *pgsql-sql@lists.postgresql.org > *Subject: *Re: Using replication to upgrade db from 12 to 16 > > Hi Frank > > > > Streaming/Physical Replication requires that both Master and Standby are > using the same OS and same PG major version. > > > > Thanks > > Kashif Zeeshan > > > > On Sat, Jul 20, 2024 at 10:01=E2=80=AFPM Frank Komsic > wrote: > > Hi, > > > > Is it possible to maintain our MASTER db in Pgsql-12 and a replica > database in Pgsql-16 as SLAVE for application testing with the latest liv= e > data? > > > > Thanks > > > Frank > > --0000000000003a97a9061db1b6fa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Frank

On Sat, Jul 20, 2024 at 11:0= 0=E2=80=AFPM Frank Komsic <ko= msicf@shoeicanada.com> wrote:

Hi Zashif,<= /u>

=C2=A0<= /span>

I read somewhere that= it was possible to have a replication on an Upgraded major version I belie= ve by using logical replication?

<= div>The restrictions I mentioned are with Physical Replication.
Y= ou can use Logical Replication which doesn't have these restrictions bu= t it has some of its own e.g.
1. It supports replication of Table= s only
2. It support only DML Commands (INSERT, UPDATE, DELETE) a= nd TRUNCATE (with some restrictions)

You can check= the restrictions=C2=A0on following link



Regards
Kashif Zeeshan

=C2=A0<= /span>

Not sure myself, but = was hoping there is a way as our application required some debugging after = the upgrade due to improper concatenation of SQL statements that was not en= forced in PGSQL-12.

=C2=A0<= /span>

Thanks

Frank

=C2=A0<= /span>

From: Kashif Zeeshan <kashi.zeeshan@gmail.com>=
Date: Saturday, July 20, 2024 at 1:45=E2=80=AFPM
To: Frank Komsic <komsicf@shoeicanada.com>
Cc: pgsql-sql@lists.postgresql.org <pgsql-sql@lists.postgresql.org><= br> Subject: Re: Using replication to upgrade db from 12 to 16=

Hi Frank

=C2=A0

Streaming/Physical Replication requires that both Ma= ster and Standby are using the same OS and same PG major version.=

=C2=A0

Thanks

Kashif Zeeshan

=C2=A0

On Sat, Jul 20, 2024 at 10:01=E2=80=AFPM Frank Komsic <komsicf@shoeicanada.com>= wrote:

Hi,

=C2=A0

Is it possible to maintain our MASTER db in Pgsql-12= and a replica database in Pgsql-16 as SLAVE for application testing with t= he latest live data?

=C2=A0

Thanks


Frank

--0000000000003a97a9061db1b6fa--