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 1soq4F-00EBob-4H for pgsql-in-general@arkaria.postgresql.org; Thu, 12 Sep 2024 20:05:28 +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 1soq4E-00GPzb-SO for pgsql-in-general@arkaria.postgresql.org; Thu, 12 Sep 2024 20:05:26 +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 1soq15-00GIzN-6o for pgsql-in-general@lists.postgresql.org; Thu, 12 Sep 2024 20:02:11 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1soq11-000rus-Rr for pgsql-in-general@postgresql.org; Thu, 12 Sep 2024 20:02:10 +0000 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a8d0d82e76aso198724066b.3 for ; Thu, 12 Sep 2024 13:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726171328; x=1726776128; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UdgcqKzig99j457kMI2G1w8/akS8fiWa1WSRE67F/Ak=; b=dko/DJ8n4qYj3HUGExr8LAUde/ckcJ4QF3DrBWurx08SbtKSjp+K0pJNjIUCacamhG 5I2LE21u91xrJyFdYjGAnhHYFAt0AmYlvJl4feg45gC/LDbsT7OYaGv5CZRuZ0FKONTA NY7hHS+uFauL7jAwYSRJUPQ+fsiIcoZ3E60YJ24PEBhe96cz0RfLDyLUt2iOd1lvig0m /RGKGy44PfSDhRt93I8pwck+BR7r+fZZwI+0BYJWiftFmD9qRFhPgw+sPeEoiVJ6rAo9 2XHOHZOhvhOPAQRfgbEmXtOc1+MqhRczG3Y1UTwZObDHRhH4SX+3cvVOxKkWofCSJ98h QV1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726171328; x=1726776128; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UdgcqKzig99j457kMI2G1w8/akS8fiWa1WSRE67F/Ak=; b=cZzARbnxgpqjbIiac/Eq/PAEnIj9rhv4TGuIB+5+DiU+paL1dFPdxhNJkadv9hrO+8 noygCjgggRpe9TSyYCwPhLCvH5088cvjLsiipCG/JVA8sgJYdzsfF7LhHwnQUA2dqWmw eVLN/8UBNK5EoiX2JZn180zxc1Guv7rO2bnjACdQ9WqPMry1n7H8Ji0LJfHiDAvG7FuT y1EPSBdLkpwlCtLynGKM/hYyIBo8wvHC0yDrrKP/n3bBD+kT3S6CfQyY5sHKOY3n0Lrx XDn/t7dChWNzD9UVvdOjJyzOQTA/kewnRu6OLkzb+/7/V7p+hj+e0zh2HoQUb+BWVz8t /O7g== X-Forwarded-Encrypted: i=1; AJvYcCV3NwU2AtBBTV9fFchiBJeHLJw+vZ4P1sqyi5ysP8lj2fO6pmsSkV9fnyif2IdqxTjzL4xPdu3zNV4zZpS+bEM2@postgresql.org X-Gm-Message-State: AOJu0YzPCasIibmW9Og+xSdL/ys6aYovTPRf0HOTZA2SnO07S7m7G/7H jSrKr9atlKi7FqS7y8JItcIUy7a1zbYKRHnlOS6U4HyXscOTSzfntq3Y87K9qpXCI9o8tdk8E8x MqQAlTG2IpZdwQKVEjwnH465Wots= X-Google-Smtp-Source: AGHT+IHM7vINRCl3h3IRSESfDHOgdKlxA+nbPKjpeRRL2evSsRso/eynJpTOj8FHRvUIdkBdQmAArtu+M8vdP+prrgY= X-Received: by 2002:a17:906:dc8f:b0:a8d:e4b:d7fe with SMTP id a640c23a62f3a-a9029106546mr394353166b.0.1726171327831; Thu, 12 Sep 2024 13:02:07 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Fri, 13 Sep 2024 01:34:40 +0530 Message-ID: Subject: pglogical selective child replication between different partition interval tables To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org, Greg Sabino Mullane Content-Type: multipart/alternative; boundary="000000000000d124090621f194c0" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d124090621f194c0 Content-Type: text/plain; charset="UTF-8" Hi Respected Team Here source side tables are created with 7 days partition interval here we have data within them changelog_event_p20240830 changelog_event_p20240906 Target side tables are created with 3 days partition interval Structure of tables at both side is same Would it be possible to replicate selective child table (changelog_event_p20240906) to target with logical replication or pglogical create publication with where clause does work in this scenario? Regards. Durga Mahesh --000000000000d124090621f194c0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Respected Team
Here source side tables are created = with 7 days partition interval here we have data within them=C2=A0

changelog_event_p20240830
changelog_event_p20240906 =C2=A0

Target side tables are created with 3= days partition interval=C2=A0
Structure=C2=A0of tables at both s= ide is same=C2=A0

Would it be possible to repl= icate selective child table (changelog_event_p20240906)=C2=A0 to target wit= h logical replication or pglogical

create publicat= ion with where clause does work in this scenario?

= Regards.
Durga Mahesh=C2=A0



--000000000000d124090621f194c0--