Re: Skipping schema changes in publication

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Shlok Kyal <shlok.kyal.oss@gmail.com>, shveta malik <shveta.malik@gmail.com>, vignesh C <vignesh21@gmail.com>, "David G. Johnston" <david.g.johnston@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-19T12:24:00Z
Lists: pgsql-hackers
On Thu, Feb 19, 2026 at 4:08 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> 3. Question, what would be the behavior of
> pg_get_publication_tables(), if we have created PUBLICATION FOR ALL
> TABLES with EXCEPT, I assume it will give all table even in the EXCEPT
> list
>

No, it won't return the tables mentioned in the except list and I
think that is what we expect from this function.

> as we have another function to get effective tables i.e.
> pg_get_publication_effective_tables(),
>

This function is for a different purpose and I think its name can be
improved, how about pg_get_publication_partitions() or something on
those lines?

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