| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | 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-18 14:24:09 |
| Message-ID: | e306d837-8505-b408-06d3-d6003e497cff@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-08-18 14:36:20 | Re: The Free Space Map: Problems and Opportunities |
| Previous Message | Robert Haas | 2021-08-18 14:23:34 | Re: .ready and .done files considered harmful |