On Thu, Jun 01, 2017 at 12:00:33AM -0400, Peter Eisentraut wrote:
> On 5/31/17 02:51, Noah Misch wrote:
> > On Tue, May 30, 2017 at 01:30:35AM +0000, Noah Misch wrote:
> >> On Thu, May 18, 2017 at 10:27:51PM -0400, Peter Eisentraut wrote:
> >>> On 5/18/17 11:11, Noah Misch wrote:
> >>>> IMMEDIATE ATTENTION REQUIRED. This PostgreSQL 10 open item is past due for
> >>>> your status update. Please reacquaint yourself with the policy on open item
> >>>> ownership[1] and then reply immediately. If I do not hear from you by
> >>>> 2017-05-19 16:00 UTC, I will transfer this item to release management team
> >>>> ownership without further notice.
> >>>
> >>> There is no progress on this issue at the moment. I will report again
> >>> next Wednesday.
> >>
> >> IMMEDIATE ATTENTION REQUIRED. This PostgreSQL 10 open item is long past due
> >> for your status update. If I do not hear one from you by 2017-05-31 02:00
> >> UTC, I will transfer this item to release management team ownership without
> >> further notice.
> >
> > This PostgreSQL 10 open item now needs a permanent owner. Would any other
> > committer like to take ownership? If this role interests you, please read
> > this thread and the policy linked above, then send an initial status update
> > bearing a date for your subsequent status update. If the item does not have a
> > permanent owner by 2017-06-03 07:00 UTC, I will investigate feature removals
> > that would resolve the item.
>
> It seems I lost track of this item between all the other ones. I will
> continue to work on this item. We have patches proposed and I will work
> on committing them until Friday.
If any other committer cares about logical replication features in v10, I'd
recommend he take ownership of this open item despite your plan to work on it.
Otherwise, if you miss fixing this on Friday, it will be too late for others
to volunteer.
> I think I now have updates posted on all my items.
As of your writing that, two of your open items had no conforming status
update, and they still don't:
- Background worker display in pg_stat_activity (logical replication especially)
- ALTER SUBSCRIPTION REFRESH and table sync worker