Horton

Re: Skipping schema changes in publication

shveta malik <shveta.malik@gmail.com>

View thread
From: shveta malik <shveta.malik@gmail.com>
To: Shlok Kyal <shlok.kyal.oss@gmail.com>
Cc: Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, Amit Kapila <amit.kapila16@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>, shveta malik <shveta.malik@gmail.com>
Date: 2025-12-08T11:57:27Z
Lists: pgsql-hackers

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.

On Thu, Dec 4, 2025 at 5:21 PM Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> I have addressed these in the v29 patch.
> Will address comments for 0003 and 0004 patch by Peter and comments by
> Shveta in next version.
>

Thanks for the patch.

I believe patch 003 (EXCEPT table) and 004 (EXCEPT column_list) should
be the primary focus. The other patches, RESET and ADD ALL tables are
additional features and may or may not be necessary depending on
further input.

I suggest making 003 and 004 as 001 and 002 respectively, and
prioritizing these first.  The RESET and ADD ALL tables patches can
become 003 and 004, and we can review them after the first 2 patches
are fully evaluated. The documentation formatting changes for ALTER
PUBLICATION are not required in this patch and, if needed, can be
handled separately.

thanks
Shveta