Request a Demo
Home   >   mailing lists

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

From Andrei Lepikhov
Subject Re: Skipping schema changes in publication
Date
Msg-id 78e4016c-b75a-4076-97b8-437d01a1563c@gmail.com
Whole thread Raw
In response to Re: Skipping schema changes in publication  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
On 7/3/26 02:11, Amit Kapila wrote:
> On Fri, Mar 6, 2026 at 6:25 PM Andrei Lepikhov <lepihov@gmail.com> wrote:
> So, to summarize based on your and Dilip's inputs, the following
> syntax will be preferable to set/reset EXCEPT list: (a) To set a
> except table list to a different list than what is defined originally,
> we will use: "ALTER PUBLICATION pub1 SET ALL TABLES EXCEPT TABLE (t1,
> ..)" (b) To reset the entire except list, we will use "ALTER
> PUBLICATION pub1 SET ALL TABLES". Do let me know if I misunderstood
> your response?
Yes, that's correct. Variants a and b seem the clearest to me.

-- 
regards, Andrei Lepikhov,
pgEdge

pgsql-hackers by date:

Previous
From: Sahitya Chandra
Date:
Subject: [PATCH] Remove trailing period from errmsg in subscriptioncmds.c
Next
From: Alexandre Felipe
Date:
Subject: Addressing buffer private reference count scalability issue