| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [BUG] wrong refresh when ALTER SUBSCRIPTION ADD/DROP PUBLICATION |
| Date: | 2021-08-23 05:01:11 |
| Message-ID: | CAA4eK1K3hkyYrNR-Dh=S=bQEOURFpTtBhLTL=rO57N-EA1N0WA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 18, 2021 at 7:54 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-08-23 05:15:07 | Re: proposal: enhancing plpgsql debug API - returns text value of variable content |
| Previous Message | Amit Kapila | 2021-08-23 04:59:14 | Re: [BUG] wrong refresh when ALTER SUBSCRIPTION ADD/DROP PUBLICATION |