Re: Skipping schema changes in publication - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Skipping schema changes in publication
Date
Msg-id CAD21AoBdE5GXw6PayASYUEkrWi6UQ6fNeOsuxf_+wVMkLZzOMA@mail.gmail.com
Whole thread Raw
In response to Re: Skipping schema changes in publication  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Skipping schema changes in publication
List pgsql-hackers
On Wed, Mar 4, 2026 at 3:01 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Mar 4, 2026 at 2:49 PM shveta malik <shveta.malik@gmail.com> wrote:
> >
> > On Wed, Mar 4, 2026 at 1:54 PM vignesh C <vignesh21@gmail.com> wrote:
> > >
> > > Here is an updated version with a couple of typos fixed and separated
> > > the describe table query based on versions which make it more easier
> > > to read.
> > >
> >
> > v56 LGTM.
> >
>
> Pushed.

Sorry for joining the discussion late.

I've tried with the new EXCEPT clause and I have some questions about
the newly introduced syntax. With this feature, we can now write:

CREATE PUBLICATION pub FOR ALL TABLES EXCEPT TABLE (a, b, c);

The exclusion table list is written in the form of TABLE (a, b, c) but
it's quite different from the inclusion table list we can specify
(e.g., TABLE a, TABLE b, TABLE c). I'm concerned that it could confuse
users. Have these points already been discussed? Also, isn't the TABLE
after EXCEPT redundant?

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Remove header lock BufferGetLSNAtomic() on architectures with 64 bit atomic operations
Next
From: Masahiko Sawada
Date:
Subject: Re: Use allocation macros in the logical replication code