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 1suQ8g-006aQS-Ru for pgsql-in-general@arkaria.postgresql.org; Sat, 28 Sep 2024 05:37:07 +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 1suQ8e-003A2o-Kk for pgsql-in-general@arkaria.postgresql.org; Sat, 28 Sep 2024 05:37:04 +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 1suQ8e-003A2g-A1 for pgsql-in-general@lists.postgresql.org; Sat, 28 Sep 2024 05:37:04 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1suQ8a-001TAP-0f for pgsql-in-general@postgresql.org; Sat, 28 Sep 2024 05:37:03 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-a93a1cda54dso367522766b.2 for ; Fri, 27 Sep 2024 22:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727501820; x=1728106620; darn=postgresql.org; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=DwDEVwhHbDQfF5Z6xOzbK2VDlYDnTBY7ZbUMyjVCXss=; b=c9rgxWl/T5rYcpXAJbU+d7CMo86xJSQVYI80K3iZa7iBvr62aSikEaPDh/nW+defdB S6yQLXaVHzxHiyUcUlNSD1SL9gx/fvbehyoe/smFyDOOhgzhVZBUp/JxnHtW0YBetbUJ GuyJeHQW6MmRjbc5aV4+8Ef71Qw7nvnX5Afe1bBwN4P7N6Jpa/W6+Xacwe8WqK5x+WmZ tetrVHqfD9cd7c3j6LNf+In54jLiUYB/TdGf9t0D1S6NudC8Tcp7cfIy35YzdjSSjjRl NJ6+7CA0A39kWmB8gWjPyYB7zS8duB1kYSwwwO2MX9il8CyhdqpMxwYOHlbNJ7mWN9we LEMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727501820; x=1728106620; h=cc: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=DwDEVwhHbDQfF5Z6xOzbK2VDlYDnTBY7ZbUMyjVCXss=; b=lw1s37vOPjb4WNLLn25koYHYzoMSioV/69eErBcqfbCydyWQUa45FOnQh1ugcc+qWl Y1tq8keFrZZoJ13f1nlUJcVfp89QOWG0FC0ZLctdo4CpFSOYEpASGJJL1PIREDptU9Qt VDEk62gszKcfhs7PfwJZtFc8dFcrljR3OygYvPpmBdnlERWzOfRY+Z5LS78sWFFqoaYC 524VJKtOTOt1/iXkKUM4QngLHkcmgqVjGID45fdQ/wWi+AGSh5iHAqGlcEsvnBsz9AtY whgy3nKemyZMEXSkSZTf9oxx0OyI9Lo/7yoYVsaF0aVNYQioUu5Dl1eagU2D+WpqDlxT d3yw== X-Forwarded-Encrypted: i=1; AJvYcCV77jQWEirNw75fckHanW2NJUQK3kmKlZymwJRm2H7KS0BhoBp2cliogbNp6Mlsr6XwdS7KF6ZHubOoGeaHVmy4@postgresql.org X-Gm-Message-State: AOJu0Yzxu2GGyPcqe64pKRBRH0VP6oCe3tyTYeMQMt+fKVsZH8jkNXRM SMnR+3zCkxlDJTxqkCxMJbMNSuMGkPvkKnsxCc43nmXQ8ucBkY1CUxLtrBB2gkEOwcPWxm6Oj5J jXAr8++XliCAru7IT+wu73i6FG2pfwB4b X-Received: by 2002:a17:906:f5a3:b0:a8a:58c5:78f1 with SMTP id a640c23a62f3a-a93c48f1bf3mt395834266b.11.1727501820194; Fri, 27 Sep 2024 22:37:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Durgamahesh Manne Date: Sat, 28 Sep 2024 11:09:51 +0530 Message-ID: Subject: Re: Regarding publish_via_partiton_root with pglogical Cc: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000058b4ec0623275cea" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000058b4ec0623275cea Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Any inputs from the PGDG team members regarding this ? Regards Durga Mahesh On Mon, Jul 22, 2024 at 3:35=E2=80=AFPM khan Affan wro= te: > Hi Durgamahesh > > In pglogical extension, there is no direct equivalent to the > publish_via_partition_root option found in the built-in logical replicati= on > > you can achieve similar results when a new partition is added; you must > add it to the replication set using pglogical.replication_set_add_table. > Similarly existing partitions are reorganized or split, ensure to update > the replication sets accordingly. > > Thanks & Regards > > > *Muhammad Affan (*=EC=95=84=ED=8C=90*)* > > *PostgreSQL Technical Support Engineer** / Pakistan R&D* > > Interlace Plaza 4th floor Twinhub office 32 I8 Markaz, Islamabad, Pakista= n > > On Sat, Jul 20, 2024 at 12:00=E2=80=AFPM Durgamahesh Manne < > maheshpostgres9@gmail.com> wrote: > >> Hi >> >> Respected Team >> >> I know the use case of implementing the partitions with publication and >> subscription of built-in logical replication >> CREATE PUBLICATION dbz_publication FOR TABLE betplacement.bet WITH >> (publish_via_partition_root =3D true); This will use parent table to rep= lica >> data changes to target from source >> But >> Could you please provide a logic to implement the same with pglogical ? >> Do i need to add this publish_via_partition_root to >> pglogical.replication_set_add_table functionality ? >> you response is valuable in this aspect >> >> Regards, >> Durga Mahesh >> > --00000000000058b4ec0623275cea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0

Any inputs from the PGDG team = members regarding this ?

Regards
Durga M= ahesh

On Mon, Jul 22, 2024 at 3:35=E2=80=AFPM khan Affan <bawag773@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
Hi=C2=A0D= urgamahesh

In pglogical extension, there is no direct eq= uivalent to the publish_via_partition_root option found in the built-in log= ical replication

you can achieve similar results=C2=A0when a new par= tition is added; you must add it to the replication set using pglogical.rep= lication_set_add_table. Similarly existing partitions are reorganized or sp= lit, ensure to update the replication sets accordingly.

<= /div>
Thanks &=C2=A0Regards

<= img width=3D"96" height=3D"71" src=3D"https://ci3.googleusercontent.com/mai= l-sig/AIorK4xPDLoHVVvHOBlBBe0cMeIZnfE5Gg8-8_LKsSpVq4Elp7C8VQOCzn4kW2pPgxDqK= kaxcjv4W7k">

Muhammad A= ffan (=EC=95=84=ED=8C=90)

PostgreSQL Technical Support Engine= er=C2=A0/ Pakistan R&D

Interlace Plaza 4th floor Twinhub office 32 I8 Ma= rkaz, Islamabad, Pakistan

On Sat, Jul 20, 20= 24 at 12:00=E2=80=AFPM Durgamahesh Manne <maheshpostgres9@gmail.com> wrote:
=
Hi

Respected Team=C2=A0

<= div>I know the use case of implementing the partitions=C2=A0with publicatio= n and subscription of built-in logical replication=C2=A0
CREATE P= UBLICATION dbz_publication FOR TABLE betplacement.bet WITH (publish_via_par= tition_root =3D true); This will use parent table to replica data changes t= o target from source=C2=A0
But
Could you please=C2= =A0provide a logic to implement the same with pglogical ?
Do i ne= ed to add this publish_via_partition_root to pglogical.replication_set_add_= table functionality ?
you response is valuable in this aspect=C2= =A0

Regards,
Durga Mahesh
--00000000000058b4ec0623275cea--