Horton
Menu

Re: Skipping schema changes in publication

Andrei Lepikhov <lepihov@gmail.com>

View thread
From: Andrei Lepikhov <lepihov@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, shveta malik <shveta.malik@gmail.com>, Shlok Kyal <shlok.kyal.oss@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, Ashutosh Sharma <ashu.coek88@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-03-08T14:37:15Z
Lists: pgsql-hackers 
On 7/3/26 02:11, Amit Kapila wrote:
> On Fri, Mar 6, 2026 at 6:25 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
> So, to summarize based on your and Dilip's inputs, the following
> syntax will be preferable to set/reset EXCEPT list: (a) To set a
> except table list to a different list than what is defined originally,
> we will use: "ALTER PUBLICATION pub1 SET ALL TABLES EXCEPT TABLE (t1,
> ..)" (b) To reset the entire except list, we will use "ALTER
> PUBLICATION pub1 SET ALL TABLES". Do let me know if I misunderstood
> your response?
Yes, that's correct. Variants a and b seem the clearest to me.

-- 
regards, Andrei Lepikhov,
pgEdge

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.