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>, vignesh C <vignesh21@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Peter Smith <smithpb2250@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-02-19T04:52:56Z
Lists: pgsql-hackers 
On Thu, Feb 19, 2026 at 10:15 AM Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> We did not implement the EXCEPT clause for ALL SEQUENCES to avoid
> additional complexity in the patch.
>

Fair enough.

> And thought of implementing it
> after this patch gets committed.
> What do you suggest? Is it ok or should we also implement EXCEPT
> clause for ALL SEQUENCES for this patch itself?
>

I am fine with doing it as a separate patch but let's try to get that
done immediately after the main patch (FOR ALL TABLES EXCEPT ...) is
committed.

-- 
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.