Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d69be-0006Ep-IC for pgsql-hackers@arkaria.postgresql.org; Thu, 04 May 2017 05:47:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d69be-0001lP-07 for pgsql-hackers@arkaria.postgresql.org; Thu, 04 May 2017 05:47:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d69a6-0005um-52 for pgsql-hackers@postgresql.org; Thu, 04 May 2017 05:45:38 +0000 Received: from mail-pg0-x242.google.com ([2607:f8b0:400e:c05::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d69Zr-00025F-JF for pgsql-hackers@postgresql.org; Thu, 04 May 2017 05:45:37 +0000 Received: by mail-pg0-x242.google.com with SMTP id i63so762316pgd.2 for ; Wed, 03 May 2017 22:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=BK6eyfCT4v4OOLLS3NeX6LEZ+G9yhK5E0HgSgaRKds4=; b=JTiv0S9a6Yr0z+IDj1hfb8KTh6O2C7jvXFt+3OVTynhVho976onLnCbAGfBoG0veZE uN1ChVnSO7yBDLcyX0Yk7INTv2Vcc91qFpacRZSvnzGnPzwxgzgG6WYXEwh5QQ8TSr/6 YZDAj3bgYg447aMlpxTikPBOjDUDEnsls55bc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=BK6eyfCT4v4OOLLS3NeX6LEZ+G9yhK5E0HgSgaRKds4=; b=Ino1myPSmJ+cKtNMnnI7PnXm2kIl9kGrdvMdTw2gmnKF722TwlUGg4EkF3rsIoQeBd MxP/yU8tsH074Q7nhwlglvMwx+QaSdGpc4kjMCDsrzYnG9OLth7JwM1JmybayFZ+O1c8 Xt+v0rjz05gyfK6+Y5yVQDh13OR2ugTatIFaQJ3+3ycWkXOmtf27+Zm9OPzsMlxpSvK1 TJbSZ8H7PIvxPlW9jFXptgQvTyCu8VYTwgOf9Rhr+V4hKHHyv1e8KO/px4VjEWM6RJj5 c/0oe4W2ywwuao0jRbBU/nsJ6aRjGo1DkNf2yO2Twq5sLVoYgQ/IkS7KfF/TqyClCFK4 w5DQ== X-Gm-Message-State: AN3rC/6w0/ljYrRgn3OXZpCZ9nAGx4apeWYeBYai6Af2VnabXsvxc7un xA3sk3IzpQiUDg== X-Received: by 10.99.121.67 with SMTP id u64mr43260725pgc.230.1493876721244; Wed, 03 May 2017 22:45:21 -0700 (PDT) Received: from rfd.leadboat.com (c-98-248-47-228.hsd1.ca.comcast.net. [98.248.47.228]) by smtp.gmail.com with ESMTPSA id v62sm1525940pfv.44.2017.05.03.22.45.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 May 2017 22:45:19 -0700 (PDT) Date: Wed, 3 May 2017 22:45:16 -0700 From: Noah Misch To: Andres Freund Cc: pgsql-hackers@postgresql.org, Peter Eisentraut , Erik Rijkers , David Steele , Petr Jelinek , Robert Haas , Craig Ringer , pgsql-hackers-owner@postgresql.org Subject: Re: snapbuild woes Message-ID: <20170504054516.GA850485@rfd.leadboat.com> References: <20170408143059.nrzuwyvv5apnhhta@alap3.anarazel.de> <20170412063142.GC2870454@tornado.leadboat.com> <20170412172151.nauhiagitlpfxief@alap3.anarazel.de> <20170413045812.GA2917375@tornado.leadboat.com> <20170417020404.GB2988768@tornado.leadboat.com> <20170418041657.hvwss6hz73ghozp5@alap3.anarazel.de> <20170422053621.2qtvurecfatet2ei@alap3.anarazel.de> <20170428043444.GD787347@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Thu, Apr 27, 2017 at 09:42:58PM -0700, Andres Freund wrote: > > > On April 27, 2017 9:34:44 PM PDT, Noah Misch 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers