From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | 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-13 05:00:26 |
Message-ID: | 20170413050026.GB2917375@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 12, 2017 at 11:02:44AM -0400, Peter Eisentraut wrote:
> On 4/9/17 22:16, Noah Misch wrote:
> > On Wed, Apr 05, 2017 at 08:25:56AM -0400, Peter Eisentraut wrote:
> >> 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.
> >
> > [Action required within three days. This is a generic notification.]
>
> Relative to some of the other open items I'm involved in, I consider
> this a low priority, so I'm not working on it right now.
By what day should the community look for your next update?
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-04-13 05:02:05 | Re: snapbuild woes |
Previous Message | Noah Misch | 2017-04-13 04:58:12 | Re: snapbuild woes |