Horton

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

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Amit Kapila <amit.kapila16@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Japin Li <japinli@hotmail.com>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-18T14:24:09Z
Lists: pgsql-hackers 
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.

Commits

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

  2. ALTER SUBSCRIPTION ... ADD/DROP PUBLICATION