| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication and inheritance |
| Date: | 2017-03-03 19:24:16 |
| Message-ID: | 147f29e5-09a4-2277-e056-0b3611784b46@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/27/17 01:57, Amit Langote wrote:
> I see that if the table is a inheritance parent, and ONLY is not
> specified, the child tables are also added to the publication.
> If the child table is later removed from the inheritance hierarchy, it
> continues to be a part of the publication.
> Perhaps that's intentional?
I came across this the other day as well. It's not clear what the best
way for this to behave would be. Another option would be to check the
then-current inheritance relationships in the output plugin.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-03-03 19:24:19 | check failure with -DRELCACHE_FORCE_RELEASE -DCLOBBER_FREED_MEMORY |
| Previous Message | Pavel Stehule | 2017-03-03 19:23:03 | Re: patch: function xmltable |