Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yz9f1-000163-BK for pgsql-hackers@arkaria.postgresql.org; Sun, 31 May 2015 20:16:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yz9f0-0000OR-No for pgsql-hackers@arkaria.postgresql.org; Sun, 31 May 2015 20:16:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Yz9ex-0000Nr-S1; Sun, 31 May 2015 20:16:39 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1Yz9eu-0006vV-KB; Sun, 31 May 2015 20:16:39 +0000 Received: by mail.anarazel.de (Postfix, from userid 108) id A9A37860002; Sun, 31 May 2015 22:16:35 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 Received: from anarazel.de (p5DDC6675.dip0.t-ipconnect.de [93.220.102.117]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 747B8860001; Sun, 31 May 2015 22:16:30 +0200 (CEST) Received: by anarazel.de (Postfix, from userid 1000) id DFE0410037E; Sun, 31 May 2015 22:16:29 +0200 (CEST) Date: Sun, 31 May 2015 22:16:29 +0200 From: Andres Freund To: Tom Lane Cc: Bruce Momjian , Michael Paquier , Robert Haas , Stephen Frost , Magnus Hagander , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release Message-ID: <20150531201629.GA32602@awork2.anarazel.de> References: <12510.1432958887@sss.pgh.pa.us> <20150530154559.GA25053@momjian.us> <20150530204727.GJ13944@alap3.anarazel.de> <20150531024845.GB13697@momjian.us> <20150531135025.GC13697@momjian.us> <20150531140305.GD13697@momjian.us> <32433.1433087744@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32433.1433087744@sss.pgh.pa.us> X-Pg-Spam-Score: -4.2 (----) 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 2015-05-31 11:55:44 -0400, Tom Lane wrote: > Bruce Momjian writes: > >> FYI, I realize that one additional thing that has discouraged code > >> reorganization is the additional backpatch overhead. I think we now > >> need to accept that our reorganization-adverse approach might have cost > >> us some reliability, and that reorganization is going to add work to > >> backpatching. > > > Actually, code reorganization in HEAD might cause backpatching to be > > more buggy, reducing reliability --- obviously we need to have a > > discussion about that. > > Commit 6b700301c36e380eb4972ab72c0e914cae60f9fd is a recent real example. > Not that that should dissuade us from ever doing any reorganizations, > but it's foolish to discount back-patching costs. On the other hand, that code is a complete maintenance nightmare. If there weren't literally dozens of places that needed to be touched to add a single parameter, it'd be far less likely for such a mistake to be made. Right now significant portions of the file differ between the branches, despite primarily minor feature additions... -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers