Re: [HACKERS] Logical replication and inheritance
| От | Peter Eisentraut |
|---|---|
| Тема | Re: [HACKERS] Logical replication and inheritance |
| Дата | |
| Msg-id | 147f29e5-09a4-2277-e056-0b3611784b46@2ndquadrant.com обсуждение |
| Ответ на | [HACKERS] Logical replication and inheritance (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>) |
| Ответы |
Re: [HACKERS] Logical replication and inheritance
|
| Список | 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
В списке pgsql-hackers по дате отправления: