Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yzf0C-0004hN-3y for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Jun 2015 05:44:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yzf0B-0002Qi-BN for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Jun 2015 05:44:39 +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 1Yzf0A-0002QW-Hc for pgsql-hackers@postgresql.org; Tue, 02 Jun 2015 05:44:38 +0000 Received: from mail-pd0-x232.google.com ([2607:f8b0:400e:c02::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Yzf06-0003Ao-KK for pgsql-hackers@postgresql.org; Tue, 02 Jun 2015 05:44:37 +0000 Received: by pdbnf5 with SMTP id nf5so63955150pdb.2 for ; Mon, 01 Jun 2015 22:44:32 -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-type:content-disposition:in-reply-to:user-agent; bh=d9/J517ZlenqLenK4qpEFARacOPuZ7Mz7rKNAPJ95So=; b=PxRM8htCt4Mq+e4HhcPPxGXtlA4i2QS7MtL9uERW1qayid/3rMowbEInDnYootMAgZ gBTQfa+DOvtMRq2yrnydSECJ1PCk2QhJBDVK/nMstnAziKQafdsE+oTfitSkdFba4L1Y j25Nx07pzY/pyNckinYSk/phl/vkkgv26J07o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=d9/J517ZlenqLenK4qpEFARacOPuZ7Mz7rKNAPJ95So=; b=h72mjsP+dmge3hWRvT09AFWgrhQ8HlpQkZZHDg2OvIollrAXOeDAkTsttK/2lBl3SW g/IMfOEFEI6574B0pNwvJfQyVKxY6efa+/KeL954cuAIZM+MwcdlDcPRW2F9UdwDx+OH EnExaam80awDcWmcATYK1sWbakYa3rcO459IRZZx0OTk2K2wSJkWwahyzUE1b2KS2BpR Gps5JIus26yIyIWpjX1kMCSsWvAi7sJglU8IizkaLn4plC4hdn1CMwFdqPdMTJYdOZIB dG4VrFjqifilCgfTN9dVx00CDZk7ZGAmq2ZaNcTFDiVek0jdKnaWzkp4oA87G7mRnovg +TUQ== X-Gm-Message-State: ALoCoQmaUyn37hmgRGAG3OXFFUFhBaan7bNXJaDMU1Gn6ZzFOAQAhNi2q6wOfvUEYp3vZpLGd1Gk X-Received: by 10.70.36.102 with SMTP id p6mr46439723pdj.18.1433223872085; Mon, 01 Jun 2015 22:44:32 -0700 (PDT) Received: from tornado.leadboat.com (c-98-248-47-228.hsd1.ca.comcast.net. [98.248.47.228]) by mx.google.com with ESMTPSA id bn5sm16096842pbc.82.2015.06.01.22.44.30 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 01 Jun 2015 22:44:31 -0700 (PDT) Date: Tue, 2 Jun 2015 01:44:29 -0400 From: Noah Misch To: David Steele Cc: "Joshua D. Drake" , Robert Haas , Bruce Momjian , Tom Lane , Andres Freund , Stephen Frost , Magnus Hagander , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release Message-ID: <20150602054429.GB50317@tornado.leadboat.com> References: <12510.1432958887@sss.pgh.pa.us> <20150530154559.GA25053@momjian.us> <556A3E26.8070902@pgmasters.net> <556A5805.5060309@commandprompt.com> <556A6908.8080600@pgmasters.net> <20150531154902.GA4798@tornado.leadboat.com> <556B322C.1070709@pgmasters.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <556B322C.1070709@pgmasters.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.7 (--) 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 Sun, May 31, 2015 at 12:09:16PM -0400, David Steele wrote: > On 5/31/15 11:49 AM, Noah Misch wrote: > > On Sat, May 30, 2015 at 09:51:04PM -0400, David Steele wrote: > >> Sure - I can write code to do that. But then why release a beta at all? > > > > It's largely for the benefit of folks planning manual, or otherwise high-cost, > > testing. If you budget for just one big test per year, make it a test of > > beta1. For inexpensive testing, you may as well ignore beta and test git > > master daily or weekly. > > I've gotten to the point of (relatively) high-cost coding/testing. The > removal of checkpoint_segments and pause_on_recovery are leading to > refactoring of not only the regressions tests but the actual backup > code. 9.5 and 8.3 are the only versions that require exceptions in the > code base. > > I've already done basic testing against 9.5 by disabling certain tests. > Now I'm at the point where I need to start modifying code to take new > 9.5 features/changes into account and make sure the regression tests > work for 8.3-9.5 with the fewest number of exceptions possible. Release of beta1 is the cue for that sort of work. > From the perspective of backup/restore testing, 9.5 has the most changes > since 9.0. I'd like to know that the API at least is stable before > investing the time in new development. Its API will be as good as pgsql-hackers could make it; beta1 is also a call for help discovering API problems we overlooked. Subsequent API changes are usually reactions to beta test reports. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers