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? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers