Re: Skipping schema changes in publication

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, YeXiu <1518981153(at)qq(dot)com>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Skipping schema changes in publication
Date: 2026-01-16 11:29:08
Message-ID: CAA4eK1KFdzZD3JvjfajhbHYYU9DErNcDVQZxfvGKv9npNfO5fQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 6, 2026 at 6:13 PM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> 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-948f8cc692d9%40eisentraut.org

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-01-16 11:31:35 Re: support ALTER COLUMN SET EXPRESSION over virtual generated column with check constraint
Previous Message Álvaro Herrera 2026-01-16 11:21:37 Re: [PATCH] psql: add \dcs to list all constraints