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 1vgi19-000p6O-1D for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Jan 2026 11:29:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vgi17-002tIR-0z for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Jan 2026 11:29:25 +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.96) (envelope-from ) id 1vgi16-002tIH-2p for pgsql-hackers@lists.postgresql.org; Fri, 16 Jan 2026 11:29:25 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vgi14-000oAQ-2z for pgsql-hackers@lists.postgresql.org; Fri, 16 Jan 2026 11:29:24 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-59b9fee282dso2029925e87.3 for ; Fri, 16 Jan 2026 03:29:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768562961; x=1769167761; 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=P/kyczep0y2zfssi1fFDP+57AWaMdKJS8uyH8mOuejA=; b=Uzv7OisFkKPJAX6+oEojIxQmLWhtCwh/dzyW1I5Ek9DSf/fal1R7EZdl1IeLfclBEF FdQBkzgoOeDqwSl/ALacT9mZlFoo6dICGTSjWpcFRFPyJT0wN1fhTC6QchS5YuXxLMyl IGWHCap0mtqBvdNBCWoXSMW/8Sf1gdi/GxMlhPHqCw/w/pQWtwhlL9vW/FsyiRE1uDrI zBwuScLz7128fEn9aWK4C6LpMqmvaxLhSbNaHIlvt8ZXO6VFK8Vo21ytvGELai1R5C1Y 10qLXEhEVla12ZfLJQRelc7nwqaUyDQwW2ywwbb2KVXUU4M4VeoqIisKOJSKYb7AhqR2 qleQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768562961; x=1769167761; 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=P/kyczep0y2zfssi1fFDP+57AWaMdKJS8uyH8mOuejA=; b=I/moAxoX7oK0JpyjnQxuhCHm+U7gBfF70rWPBqIHwbUhxCUmihzhvIt1MHvYS0xqHW e9rC1Y2RGvptkqSzh6ayKkXHTZxoZUMZ8Oz4elHEGW5JSbtr5t1ddsOBqQpMx7Olm7fs cfIBYy+aV9zJ01TXco8JP/K+u00eCXwRWpOtT9hQf2vkD11x1t87UBIzQtz/aO3hduiL wUE6xtHUMVUUDUniY5ow4Th6fw8LOFib9DBw7FvIlwiFBYhipSnU1WDaG5aXC6lEYxhV PzFV5GHSjaWwOZviiFlhyr2UIzi423sN7Hpoc0DsQHtRjFc2ncPFYvaLAFLlnn2FsWvc 6U9A== X-Forwarded-Encrypted: i=1; AJvYcCUfirUC4JF/rz/RcyNWG8E1Ak3HtnOxJ06Ccqd+DZ3d++uZjCjJr++Vl0XcO0g3YpMHgsZmnm+x3AyDa/vY@lists.postgresql.org X-Gm-Message-State: AOJu0YwEaEZEcz9SWsTOUcj861PpxYwfHLUE5jZIvx3DBcgc0OzNwoFd /tMfWykz/BhHYGY9mfBvTcex7adfIBPeGOhPZ4R1up5ce50LMEiK730hFKQodJTSt/Uj7D8re4s kTzEMYS1KD5hQIsgVqSSTMBXc+KOPU8g= X-Gm-Gg: AY/fxX682T5+XNFxGEK+4nBVftKzlue1lq/O7J33Sj/VRNWJSNAM9XIlPpnpwrk7Fc+ FKzvhZUB45wIR360LZWehyAt3BHQpGnes/VnQk/T2KEJJsVkAbGKxCWWv+W5gw/hUkRdLSS9Yd/ wpWnbl8Qf/yNdrbZk+zRHZC4tqanF9PQJvr09MT8udmeQQ9c4xvOgR351OdZL1SGaZNB0Shw4Z6 BedJ7HLvyAhmAoqcWj72OECwUqnbDtsvZWAZaKDdoZ63/A4D2F/Vwgjy27v5M+9PDfTENAcYWF4 zV/H6xRcndr0XbkvZGYMj16+jVnfQA== X-Received: by 2002:a05:6512:1050:b0:59b:7a80:3b66 with SMTP id 2adb3069b0e04-59baeef85e9mr851612e87.35.1768562960802; Fri, 16 Jan 2026 03:29:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Fri, 16 Jan 2026 16:59:08 +0530 X-Gm-Features: AZwV_Qj8yA1CG_UO5RHNmTLxSRwjbAS4o7uFT8VAtuLSrXelz2iKt3UTTrk5lAI Message-ID: Subject: Re: Skipping schema changes in publication To: Shlok Kyal Cc: shveta malik , Peter Smith , vignesh C , "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 Tue, Jan 6, 2026 at 6:13=E2=80=AFPM Shlok Kyal wrote: > > Also addressed the remaining comments. I have also addressed the > comments by Peter in [1]. I have also done some minor cosmetic > changes. > CREATE PUBLICATION pub1 FOR ALL TABLES EXCEPT TABLE (t1,t2); Did we consider using EXCLUDE instead of EXCEPT? In another similar feature being discussed, the community is proposing to use EXCLUDE to SQL Standard, so won't it be better to use EXCLUDE here as well? [1] - https://www.postgresql.org/message-id/63e1587b-4258-41de-b823-948f8cc= 692d9%40eisentraut.org --=20 With Regards, Amit Kapila.