Re: Support EXCEPT for TABLES IN SCHEMA publications

Peter Smith <smithpb2250@gmail.com>

From: Peter Smith <smithpb2250@gmail.com>
To: Nisha Moond <nisha.moond412@gmail.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Zsolt Parragi <zsolt.parragi@percona.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-06-22T23:40:47Z
Lists: pgsql-hackers
On Tue, Jun 23, 2026 at 12:49 AM Nisha Moond <nisha.moond412@gmail.com> wrote:
>
...
>
> Based on the changes in commit 77b6dd9, I re-analyzed the pointed-out paragraph.
>
> On reconsideration, I think the schema-move behavior is really a
> property of EXCEPT itself rather than ALTER PUBLICATION. So we can
> keep it only in the CREATE PUBLICATION documentation and drop it from
> ALTER PUBLICATION to avoid duplication.
> We already have a cross-reference in ALTER PUBLICATION: "See CREATE
> PUBLICATION for further details on the semantics of EXCEPT", so users
> still have a clear path to the detailed behavior description.
> I modified your suggestion slightly to keep the information from the
> removed paragraph intact.
>
> Attached updated patches v16. No changes in 0001 to 0003.
>

Hi Nisha.

Thanks for all the changes. I don't have any more review comments at this time.

======
Kind Regards,
Peter Smith.
Fujitsu Australia



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.