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 1sV45T-007eFK-N9 for pgsql-general@arkaria.postgresql.org; Sat, 20 Jul 2024 07:00:59 +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 1sV44T-00D2kE-Jl for pgsql-general@arkaria.postgresql.org; Sat, 20 Jul 2024 06:59:58 +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 1sV44T-00D2j2-8e for pgsql-general@lists.postgresql.org; Sat, 20 Jul 2024 06:59:57 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sV44S-000W4a-2H for pgsql-general@lists.postgresql.org; Sat, 20 Jul 2024 06:59:57 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a77e5929033so276663066b.0 for ; Fri, 19 Jul 2024 23:59:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721458794; x=1722063594; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=YgqeFRxTKE9Yvu7WO7z6g6ZO6v0NrlZg9N48yketXtk=; b=Lj5NqnHm3SX5nkUEfO7IuYBik1B/Ez6tQZwcMBXkjQGUTVY+L0UVyPzjozz5iEDAJf JgF3jHGT7heXBVqVcjweb0s20h9YbRm+Rd4HfWA3Jb1pyLvezxDSHFl0dn7pkWpbQby8 QhtmpM3UczSxSQEtPNkNldTa0lWXiLlKOJjBcoZAT86wAhtGoJYRv+I3QFAa7iv2FNEH T+1T3GZz3Lgo9xSS3AxpaLaInySThOZElpt0fWuG9S6LJ75GFF6AheWF2DKhpUBKxUQD eC+58rTb/s49Azjtte7cFNB3vXTOkaEO3ElIC9njtlUswkwgVkK5ktSridytJ+2ovRO6 l3Dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721458794; x=1722063594; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=YgqeFRxTKE9Yvu7WO7z6g6ZO6v0NrlZg9N48yketXtk=; b=aOU7EoCqiAY+HITlEQg6LEEYbhJTMPOkrVf1T1zqavysbnpG7euV/N+yf3f6TSi3jv CIvk9iQHzLkKD8+PvNPGIk4nuIEKZm7qFBK4a1Lk+k1JUisLWquiwQp/OnlksVGXwWXU DwLpRfwcf+sHKBxfCmSBG7+t1pB8kEWgy94OGqm3Wrss6aTluUcG1Q5HS4Qi3XpcvCBf JOZs/910CtC/vVtFXico6Xv4Cg3/AOq0FsPQu7VMd2inR05cpcd3d8yE4TNL4iOKOCFD qPcFABUcD2SAVxNYKZuPUDkE4AK4hXh+qt33Aygby8ajRWsTY9Rqz0amrNeXiojBHJ1F KpaQ== X-Gm-Message-State: AOJu0YxOtZsbhBXwVDeZ0GuU4mdkt47tSsbhu7a93A63MohwfVUA4snR JW0C31aDdDlfk+FLfEfe3rGcDQJ1JQn0SmZyLOz8DaBV5BPYYTxUa/pPdP+IkB9hYHNbDDUTSpX ajhoCadj8FRgIixbNhNUffBaX07Bjho/naI0= X-Google-Smtp-Source: AGHT+IGzlPyJZV0PDQnL9OqZDfFXkZQpgOJardrQpMFk8Ts9wSo7kbjOMcF7wMLaD0+aDHcR35VI70ap6cP7v7Mu8zg= X-Received: by 2002:a17:907:7296:b0:a79:8149:966e with SMTP id a640c23a62f3a-a7a4bfe6355mr49456766b.1.1721458793492; Fri, 19 Jul 2024 23:59:53 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Sat, 20 Jul 2024 12:31:04 +0530 Message-ID: Subject: Regarding publish_via_partiton_root with pglogical To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000e1b5d0061da85baf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e1b5d0061da85baf Content-Type: text/plain; charset="UTF-8" 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 = true); This will use parent table to replica 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 --000000000000e1b5d0061da85baf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi

Respected Team=C2=A0

I know the use case of implementing the partitions=C2= =A0with publication and subscription of built-in logical replication=C2=A0<= /div>
CREATE PUBLICATION dbz_publication FOR TABLE betplacement.bet WIT= H (publish_via_partition_root =3D true); This will use parent table to repl= ica data changes to target from source=C2=A0
But
Co= uld you please=C2=A0provide a logic to implement the same with pglogical ?<= /div>
Do i need to add this publish_via_partition_root to pglogical.rep= lication_set_add_table functionality ?
you response is valuable i= n this aspect=C2=A0

Regards,
Durga Mahes= h
--000000000000e1b5d0061da85baf--