Horton
Menu

Re: Skipping schema changes in publication

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: shveta malik <shveta.malik@gmail.com>
Cc: vignesh C <vignesh21@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-06T03:23:30Z
Lists: pgsql-hackers 
On Thu, Mar 5, 2026 at 5:22 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> 2)
> postgres=# ALTER TABLE tab_top_root ATTACH PARTITION tab_root FOR
> VALUES FROM (0) TO (2000);
> ERROR:  cannot attach table "tab_root" as partition because it is
> referenced in publications "pub1", "pub3" EXCEPT clause
> DETAIL:  The publication EXCEPT clause cannot contain tables that are
> partitions.
> HINT:  Modify the publication's EXCEPT clause using ALTER PUBLICATION
> ... SET EXCEPT TABLE or DROP EXCEPT TABLE before attaching the table.
>
> Shall we shorten the HINT slightly? Is it necessary to explicitly say
> "before attaching the table", or can we omit it? Thoughts?
>

I think we can omit it.

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