Re: How can we make beta testing better?

From: Greg Stark <stark(at)mit(dot)edu>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: MauMau <maumau307(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: How can we make beta testing better?
Date: 2014-04-18 16:43:08
Message-ID: CAM-w4HPN6Be749t3s6jdKd7oKsxgvg1TK3uDhCpYg912M9b_qg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 18, 2014 at 4:15 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> There was no reply, which I took as "this isn't a
> new feature and isn't user visible anyway, so what would be the point?"

To be fair the list was pretty long already. And like regression
testing, coming up with a list of things to test is kind of beside the
point. If we knew which things had to be tested then we would have
tested them already. The point of beta testing is to have people run
their applications on it in case their applications are doing stuff we
*didn't* anticipate needing to test.

I think the take-away here is that testing for long periods of time
under load and while using the full suite of complex configurations
simultaneously that they use in production (such as hot standby
replicas to spread load) is what's important.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2014-04-18 16:44:48 Re: DISCARD ALL (Again)
Previous Message Andrew Dunstan 2014-04-18 16:42:58 Re: assertion failure 9.3.4