Date: Wed, 12 Apr 2017 06:31:42 +0000
From: Noah Misch <noah@leadboat.com>
To: peter.eisentraut@2ndquadrant.com
Cc: Andres Freund <andres@anarazel.de>, Erik Rijkers <er@xs4all.nl>,
	David Steele <david@pgmasters.net>,
	Petr Jelinek <petr.jelinek@2ndquadrant.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	Robert Haas <robertmhaas@gmail.com>,
	Craig Ringer <craig@2ndquadrant.com>,
	pgsql-hackers-owner@postgresql.org
Subject: Re: snapbuild woes
Message-ID: <20170412063142.GC2870454@tornado.leadboat.com>
References: <7286ebe9-cb1b-cf1a-f85b-fbe3402ea0bf@2ndquadrant.com>
 <9a897b86-46e1-9915-ee4c-da02e4ff6a95@2ndquadrant.com>
 <51f65289-54f8-2256-d107-937d662d69f1@2ndquadrant.com>
 <f41d64c7-1ae2-fac7-bf7f-f24dfe2d33bd@2ndquadrant.com>
 <edd7316a312a869c6548d20439be3708@xs4all.nl>
 <b81b0426-68e3-aea3-eb3f-e56d53f0779c@2ndquadrant.com>
 <6e0a391d-d85a-dbf6-ce33-4c26a486e909@pgmasters.net>
 <20170408135659.ersubdrhjp736nob@alap3.anarazel.de>
 <aac311f8b41582e08ccb127d3a553e0d@xs4all.nl>
 <20170408143059.nrzuwyvv5apnhhta@alap3.anarazel.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170408143059.nrzuwyvv5apnhhta@alap3.anarazel.de>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On Sat, Apr 08, 2017 at 07:30:59AM -0700, Andres Freund wrote:
> On 2017-04-08 16:29:10 +0200, Erik Rijkers wrote:
> > On 2017-04-08 15:56, Andres Freund wrote:
> > > On 2017-04-08 09:51:39 -0400, David Steele wrote:
> > > > On 3/2/17 7:54 PM, Petr Jelinek wrote:
> > > > >
> > > > > Yes the copy patch needs rebase as well. But these ones are fine.
> > > > 
> > > > This bug has been moved to CF 2017-07.
> > > 
> > > FWIW, as these are bug-fixes that need to be backpatched, I do plan to
> > > work on them soon.
> > > 
> > 
> > CF 2017-07 pertains to postgres 11, is that right?
> > 
> > But I hope you mean to commit these snapbuild patches before the postgres 10
> > release?  As far as I know, logical replication is still very broken without
> > them (or at least some of that set of 5 patches - I don't know which ones
> > are essential and which may not be).
> 
> Yes, these should go into 10 *and* earlier releases, and I don't plan to
> wait for 2017-07.

[Action required within three days.  This is a generic notification.]

The above-described topic is currently a PostgreSQL 10 open item.  Peter,
since you committed the patch believed to have created it, you own this open
item.  If some other commit is more relevant or if this does not belong as a
v10 open item, please let us know.  Otherwise, please observe the policy on
open item ownership[1] and send a status update within three calendar days of
this message.  Include a date for your subsequent status update.  Testers may
discover new open items at any time, and I want to plan to get them all fixed
well in advance of shipping v10.  Consequently, I will appreciate your efforts
toward speedy resolution.  Thanks.

[1] 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