Re: Support EXCEPT for TABLES IN SCHEMA publications

Zsolt Parragi <zsolt.parragi@percona.com>

From: Zsolt Parragi <zsolt.parragi@percona.com>
To: pgsql-hackers@lists.postgresql.org
Date: 2026-06-10T20:54:15Z
Lists: pgsql-hackers
> Let's wait for feedback from others.

Yes, I think that's the best approach for this question.

> Right, As also mentioned above, ALTER TABLE changes that affect
> publication membership currently do not emit any notice or warning, so
> I'm not sure we need one here either.

My idea was to make this change both for existing cases and new cases
in this patch, so it would be consistent, but that wasn't exactly
clear in my previous email, sorry about that. Similarly to how cascade
reports additional objects being dropped.



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Doc: Clarify that publication exclusions track table identity.