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.96) (envelope-from ) id 1vp1vm-00HVMu-2E for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Feb 2026 10:22:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vp1ul-007tmR-0f for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Feb 2026 10:21:15 +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.96) (envelope-from ) id 1vp1uk-007tmI-1v for pgsql-hackers@lists.postgresql.org; Sun, 08 Feb 2026 10:21:14 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vp1ui-000000017De-0G8A for pgsql-hackers@lists.postgresql.org; Sun, 08 Feb 2026 10:21:13 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-385bc6910eeso27188121fa.2 for ; Sun, 08 Feb 2026 02:21:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1770546070; cv=none; d=google.com; s=arc-20240605; b=XeEBPaPrCVmTD0osAOnspoR1JnXyQQFAjwaQVzaDQ2R8jAlcbiNJVU3+q/JW4L1hlt UfGOq6W1BA8tLE5ey13qJqrfiizWUD+l05N0jvZDKnbqcvB0bJHtvoYHwKhc0qYsP1Q8 JTBfGKHT8B/86Q9gfl3oD95xNCmgRJ2W6xQP/kgljux6nctSMZzw/p2HHjntLX6K6yl+ +tgkWfytAjgbcq2vkZ25wU0x5vARqkkB4ibuI+M+DRclo/qO1M1jfkHrgFXMAlioFc/u XhQbn3GFycB9HH8D5joTIgbHjR3bNT6vAQZ4jXvqquLhL68jsAEkIbuzsqTxu4osL5P5 9uoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=c886mounqoSM3WL2CW3KNfYAoPBw0i75qgalO6CT6hc=; fh=JFtscygGyneBKFze9V7pZH39kz3FrVkVPkmIBDCkXZI=; b=kpFNYgmcW/FFHQhP3Q1eUDcF0L48nx7mTINcfm5TLtek8n6QrMsGK2RFDYk3yc9kVa 3N1skBD4ngIF29nD2WLOsstYgo+JiJLupW0X5xtQn3L2drSMwYEvz/0l2famVHieW3tt pj+8gKBb26ciRbGznmo4iqash43wFkiC43/LtuqZssULqRHXP6ad1KabXkuGznCtM258 L+AvDi7EGzBukZtlHQmgdR/VXfp5my5zjQt62Jo0/Azm6ZNTLDB//JpGlmB6Tgxy497B t4+9LrlGTrqEQmgspG597pB9gpOfPsBah32+ngomp/cpOJPV85CgyO+s5SgEIOe3uFmU e61w==; darn=lists.postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1770546070; x=1771150870; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=c886mounqoSM3WL2CW3KNfYAoPBw0i75qgalO6CT6hc=; b=Q1n+YV907nNzipfjBajz0SM6uPBMpZ+stZn2mEGl3iNozgoK7xC3BL0aOz7Q6pXhy3 W0DW+DNFHCfbSA2km2vASG7XzDH69horsaaki4/a+ThWBPAAL+uK0//r1lyjGIzJZ4rr FzxaJE21HsNFMDsKObKemYBWdwSr04qpWjLHFLLL+AHcHwtQEjiF4fb8nEN5OXQp/GgR VJaJx35BsaNCk8/rYKl45Zq5m2AClA80yfiFi4m1QhtVNnMDVTvXO/uDyTAoxuzHnZZg l5tT+jGhhnjCbvPmeNYtt+yU6XOgnDKOi+jGqYbTzbFVBVMdn3kpSA5CvUyygi0X0FmM O3AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770546070; x=1771150870; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=c886mounqoSM3WL2CW3KNfYAoPBw0i75qgalO6CT6hc=; b=FxXLwhzj9TJFR3+wubX5sxHTad9N0Gfd2exonCYqrQJdYM/KcZzBTKfPTN2mFglu7c WwD3St0/Ke4/DVq9QPzTDWksKZ0U2utWjF+fi6eF5qnqWAvcRms++MG4gyPrPwdo3m7/ dokoBV1atfSWLzOC/NzrKAzKhNcXdNLrE3lhZWZqFsTZPOo1wKEqEzSwiHxPAJggIpEU SJtgiM9sC6AWVDtjckD6zwoneJQTbxj166RGo5TR70HCrBuEp8kMLtCbJSl4tv3pMnZU Lusd0znnt9wMiXqw+W79XqKf25rzCF4MRVgyulOMvN/EmJqxp9+fr6dsxdQJzfjTF8TN p5Sg== X-Forwarded-Encrypted: i=1; AJvYcCXy6Qx/38LXamfHjxfwBauH7uKzIEjLsqmFPxeIDrjEkEDdtoNzPo4yCcpqgqIXAVOpzT6KE9bQ9JoSVZoK@lists.postgresql.org X-Gm-Message-State: AOJu0Yyhc89yO28WOmB2jU4tRj+1f2eGRCl7izKxQIIcVFMDLc/HW5CF xg9dZ4G0vW1n++ux0+QbRH8JEz4inWA/be9/gIgzL/9ilxpHIpC25lk+9SaRDMLbocNI0Ws7muz eLHeGgoNZrqCS3JgkGGId1L3QGE1g4DM= X-Gm-Gg: AZuq6aKAg87vxyl9BYAJUf7ghSdFleaoiWRfLrNyuRH9MgkRoNtZYqQNRtgtT9An8wC Rg8Rrf6XrDf5HlOr9X43RyXg7JUR2RTXY33J9m3CeJ4g4zH6EMJnRrR3Cm8CedfAKcZQxmPQyMG Uvw21vzr0B0C1MQmTv5segrJ7Wm76gIOaQ8r+M1ttDjdWWhJW1IP/MGIR125NAimQ1RO7PMRPNm f9vCrCaCETuznidGI3LQFSvStJwKcJo8QrxAc1n+5U6QcnfeBDrs8I3NmAfglCekamF9RKSwUY+ LxT9c11/LSJ0RcfVZ9reADdLTREvZvg6AfpTwpSMGwvGZ/Cz9nYbi9LN0LdCwIaV5UZnbJY= X-Received: by 2002:a05:651c:19a7:b0:386:9653:5d5c with SMTP id 38308e7fff4ca-386b4e7d341mr24315091fa.8.1770546070016; Sun, 08 Feb 2026 02:21:10 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Sun, 8 Feb 2026 15:50:58 +0530 X-Gm-Features: AZwV_Qgq2DzMFhN7vLG-tj6NJ6VqHoSIodqv6qOsVDgMbL3V0ZaF_XOXaMqXg5w Message-ID: Subject: Re: Skipping schema changes in publication To: shveta malik Cc: Shlok Kyal , vignesh C , Dilip Kumar , Peter Smith , "Zhijie Hou (Fujitsu)" , YeXiu <1518981153@qq.com>, Ian Lawrence Barwick , Bharath Rupireddy , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Feb 6, 2026 at 3:54=E2=80=AFPM shveta malik wrote: > > On Thu, Feb 5, 2026 at 10:59=E2=80=AFAM Shlok Kyal wrote: > > > > I have added the fix of the same in the latest v41 patch and added the > > corresponding test in 101_test.pl file. > > I have also merged the v40-0001 and v40-0002 patches to form v41-0001 > > patch and v41-0002 has the extended tests. > > > > Thank You for the patched Shlok. While testing I found a case where > table-sync and incremental-sync are not replicating same set of > tables. > > I have attached the test-case and results in DifferentPubViaRoot.txt > > The problem happens when we have a subscriber subscribing to multiple > pubs with different EXCEPT and different PUBLISH_VIA_PARTITION_ROOT > value. Example: > > CREATE PUBLICATION pub1 for ALL TABLES EXCEPT table (tab_part_1_p1, > tab_part_2_p2) WITH (PUBLISH_VIA_PARTITION_ROOT=3Dtrue); > CREATE PUBLICATION pub2 for ALL TABLES EXCEPT table (tab_part_2) WITH > (PUBLISH_VIA_PARTITION_ROOT=3Dfalse); > > We need to decide the behaviour of such a case for Apporach1. > It is better to disallow such combinations where combining publications could lead to contradictory behavior. For example, pub1: FOR ALL Tables EXCEPT (tab1) and pub2: FOR TABLE tab1. Now, combining pub1 and pub2 via subscription should result in an ERROR. We have similar restrictions for column lists. See section: "Warning: Combining Column Lists from Multiple Publications" in docs [1]. Does that sound reasonable to you? [1] - https://www.postgresql.org/docs/devel/logical-replication-col-lists.h= tml --=20 With Regards, Amit Kapila.