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

On Fri, Mar 6, 2026 at 1:47 PM vignesh C <vignesh21@gmail.com> wrote:
>

Instead of a syntax like "ALTER PUBLICATION pub1 DROP EXCEPT TABLE t1"
to allow resetting the entire except list by incrementally dropping
the except tables, I could think of following alternatives

Option-1: ALTER PUBLICATION pub1 SET ALL TABLES; This suggests it is
still an ALL TABLES publication, but providing a new definition. Since
it didn't include an EXCEPT clause this time, the exception list is
now empty.

Option-2: ALTER PUBLICATION pub1 SET EXCEPT TABLE DEFAULT; Since the
"default" state of an ALL TABLES publication is to have zero
exceptions, the "default" will serve as an alias for an empty list.

If we follow the first one, then we can choose "ALTER PUBLICATION pub1
SET ALL TABLES EXCEPT TABLE (t1)" to set a new except list instead of
"ALTER PUBLICATION pub1 SET EXCEPT TABLE (t1)"

--
With Regards,
Amit Kapila.