| 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-04-05 12:25:56 |
| Message-ID: | 0435c691-367a-292f-7bd7-84d7cd2970cc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
After thinking about it some more, I think the behavior we want would be
that changes to inheritance would reflect in the publication membership.
So if you have a partitioned table, adding more partitions over time
would automatically add them to the publication.
We could implement this either by updating pg_publication_rel as
inheritance changes, or perhaps more easily by checking and expanding
inheritance in the output plugin/walsender. There might be subtle
behavioral differences between those two approaches that we should think
through. But I think one of these two should be done.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitaly Burovoy | 2017-04-05 12:36:41 | Re: identity columns |
| Previous Message | Ronan Dunklau | 2017-04-05 12:00:54 | Re: [Proposal] Make the optimiser aware of partitions ordering |