Re: snapbuild woes

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, David Steele <david(at)pgmasters(dot)net>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-hackers-owner(at)postgresql(dot)org
Subject: Re: snapbuild woes
Date: 2017-05-04 05:45:16
Message-ID: 20170504054516.GA850485@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 27, 2017 at 09:42:58PM -0700, Andres Freund wrote:
>
>
> On April 27, 2017 9:34:44 PM PDT, Noah Misch <noah(at)leadboat(dot)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
> >see
> >> > 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
> >we'll
> >> > have something in tree by end of this week, if not I'll send an
> >update.
> >>
> >> I was less productive this week than I'd hoped, and creating a
> >testsuite
> >> was more work than I'd anticipated, so I'm slightly lagging behind.
> >I
> >> 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
> >status
> >update. Refer to the policy on open item ownership:
> >https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com
>
> 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 wrong...

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
update.

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:
https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2017-05-04 06:32:33 Re: snapbuild woes
Previous Message Jeff Davis 2017-05-04 05:44:54 Re: [POC] hash partitioning