Re: [BUG] wrong refresh when ALTER SUBSCRIPTION ADD/DROP PUBLICATION

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Japin Li <japinli@hotmail.com>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-23T05:01:11Z
Lists: pgsql-hackers
On Wed, Aug 18, 2021 at 7:54 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 10.08.21 05:22, Amit Kapila wrote:
> > Yeah, unless we change design drastically we might not be able to do a
> > refresh for dropped publications, for add it is possible. It seems
> > most of the people responded on this thread that we can be consistent
> > in terms of refreshing for add/drop at this stage but we can still go
> > with another option where we can refresh only newly added publications
> > for add but for drop refresh all publications.
> >
> > Peter E., do you have any opinion on this matter?
>
> Refresh everything for both ADD and DROP makes sense to me.
>

Thanks for your suggestion.

-- 
With Regards,
Amit Kapila.



Commits

  1. Fix Alter Subscription's Add/Drop Publication behavior.

  2. ALTER SUBSCRIPTION ... ADD/DROP PUBLICATION