From: David Steele <david@pgmasters.net>
To: Noah Misch <noah@leadboat.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: pgsql-core <pgsql-core@postgresql.org>
Subject: Re: [CORE] postpone next week's release
Date: Sun, 31 May 2015 12:09:16 -0400
Message-ID: <556B322C.1070709@pgmasters.net> (raw)
In-Reply-To: <20150531154902.GA4798@tornado.leadboat.com>
References: <CA+Tgmoa6hekDGenr29TG_K4bH7rxLEM9RU+5KDAiY+SiAsFhew@mail.gmail.com>
<20150529223321.GB6535@alap3.anarazel.de>
<CA+TgmoYSO0a9YDe2bhpZoPgO4m62CyQL26LRkCQ8=vrQ8ZwdXA@mail.gmail.com>
<12510.1432958887@sss.pgh.pa.us>
<CA+TgmoYovkev0xXnxaTD8vnt=M9Cn+RmOkVEouqwj6_9JLkzLw@mail.gmail.com>
<20150530154559.GA25053@momjian.us>
<CA+TgmoYHeUtO=MUUMOPQdvTj4Gpm02gtt+F6hfOreN8nYo-x9Q@mail.gmail.com>
<556A3E26.8070902@pgmasters.net>
<556A5805.5060309@commandprompt.com>
<556A6908.8080600@pgmasters.net>
<20150531154902.GA4798@tornado.leadboat.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 5/31/15 11:49 AM, Noah Misch wrote:
> On Sat, May 30, 2015 at 09:51:04PM -0400, David Steele wrote:
>> On 5/30/15 8:38 PM, Joshua D. Drake wrote:
>>> On 05/30/2015 03:48 PM, David Steele wrote:
>>>> I would argue Heikki's WAL stuff is a perfect case for releasing a
>>>> public alpha/beta soon. I'd love to test PgBackRest with an "official"
>>>> 9.5dev build. The PgBackRest test suite has lots of tests that run on
>>>> versions 8.3+ and might well shake out any bugs that are lying around.
>>>
>>> You are right. Clone git, run it nightly automated and please, please
>>> report anything you find. There is no reason for a tagged release for
>>> that. Consider it a custom, purpose built, build-test farm.
>>
>> 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.
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.
Perhaps I'm just misunderstanding the nature of the discussion.
--
- David Steele
david@pgmasters.net
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: david@pgmasters.net, noah@leadboat.com, jd@commandprompt.com, robertmhaas@gmail.com, bruce@momjian.us, tgl@sss.pgh.pa.us, andres@anarazel.de, sfrost@snowman.net, magnus@hagander.net, pgsql-core@postgresql.org
Subject: Re: [CORE] postpone next week's release
In-Reply-To: <556B322C.1070709@pgmasters.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox