Horton
Menu

Re: Skipping schema changes in publication

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Shlok Kyal <shlok.kyal.oss@gmail.com>
Cc: shveta malik <shveta.malik@gmail.com>, Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, YeXiu <1518981153@qq.com>, Ian Lawrence Barwick <barwick@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-16T11:29:08Z
Lists: pgsql-hackers 
On Tue, Jan 6, 2026 at 6:13 PM Shlok Kyal <shlok.kyal.oss@gmail.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.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix miscellaneous issues in EXCEPT publication clause.

  2. Change syntax of EXCEPT TABLE clause in publication commands.

  3. Add support for EXCEPT TABLE in ALTER PUBLICATION.

  4. Allow table exclusions in publications via EXCEPT TABLE.

  5. Add wait_for_subscription_sync for TAP tests.