Re: Skipping schema changes in publication

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Peter Smith <smithpb2250@gmail.com>, Shlok Kyal <shlok.kyal.oss@gmail.com>, vignesh C <vignesh21@gmail.com>, shveta malik <shveta.malik@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Nisha Moond <nisha.moond412@gmail.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, "David G. Johnston" <david.g.johnston@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-03-30T04:11:33Z
Lists: pgsql-hackers
On Mon, Mar 30, 2026 at 9:37 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Mar 30, 2026 at 8:02 AM Peter Smith <smithpb2250@gmail.com> wrote:
> >
> > ~~~
> >
> > EXCEPT:
> >
> > 3.
> >     <varlistentry id="sql-createpublication-params-for-except-table">
> > -    <term><literal>EXCEPT TABLE</literal></term>
> > +    <term><literal>EXCEPT</literal></term>
> >      <listitem>
> >
> > The 'EXCEPT' clause is not really at the same level as all the other
> > ones, because it can only be applied to the FOR ALL TABLES. So, I felt
> > maybe 'EXCEPT' might make more sense as a sublist entry under the FOR
> > ALL TABLES clause.
> >
>
> Possible but in future it would be applicable for all the three
> variants listed above: FOR TABLES IN SCHEMA, FOR ALL TABLES, FOR ALL
> SEQUENCES. So, don't think making it as a sublist for "FOR ALL TABLE"
> is a good idea. I find keeping it at its current place okay as it is
> also an independent clause.

Keeping it independent makes sense, as it will allow for easier future
expansion.

-- 
Regards,
Dilip Kumar
Google



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.