On Thu, Apr 27, 2017 at 09:42:58PM -0700, Andres Freund wrote:
> On April 27, 2017 9:34:44 PM PDT, Noah Misch <n...@leadboat.com> wrote:
> >On Fri, Apr 21, 2017 at 10:36:21PM -0700, Andres Freund wrote:
> >> On 2017-04-17 21:16:57 -0700, Andres Freund wrote:
> >> > I've since the previous update reviewed Petr's patch, which he
> >since has
> >> > updated over the weekend. I'll do another round tomorrow, and will
> >> > how it looks. I think we might need some more tests for this to be
> >> > committable, so it might not become committable tomorrow. I hope
> >> > have something in tree by end of this week, if not I'll send an
> >> I was less productive this week than I'd hoped, and creating a
> >> was more work than I'd anticipated, so I'm slightly lagging behind.
> >> hope to have a patchset tomorrow, aiming to commit something
> >> Monday/Tuesday.
> >This PostgreSQL 10 open item is past due for your status update.
> >Kindly send
> >a status update within 24 hours, and include a date for your subsequent
> >update. Refer to the policy on open item ownership:
> I committed part of the series today, plan to continue doing so over the next
> few days. Changes require careful review & testing, this is easy to get
This PostgreSQL 10 open item is past due for your status update. Kindly send
a status update within 24 hours, and include a date for your subsequent status
Also, this open item has been alive for three weeks, well above guideline. I
understand it's a tricky bug, but I'm worried this isn't on track to end.
What is missing to make it end?
Refer to the policy on open item ownership:
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: