From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.5 release timetable, again |
Date: | 2009-08-27 15:29:42 |
Message-ID: | 4059.1251386982@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Well, I wasn't suggesting adding a lot more testing of things that
> we're already testing. I was assuming that we would craft the
> additional tests to hit areas that we are not now covering well. My
> point here is only to what Peter said upthread: we want to be able to
> get positive results rather than waiting for "enough" negative results
> (whatever that means). To get positive results, you must have a test
> suite. While letting beta testers test whatever they want has some
> value, testing things we think might be likely hiding places for bugs
> (such as WAL recovery) has merit, too. Making those tests
> well-organized and easily repeatable is, IMHO, a Good Thing.
The problem here is the "easily repeatable" bit. Almost by definition,
easily repeatable tests don't find hard-to-reproduce problems. I don't
mean to suggest that they're without value, but they are no substitute
for beta testers doing unpredictable things.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-08-27 15:31:56 | Re: BUG #4996: postgres.exe memory consumption keeps going up |
Previous Message | Magnus Hagander | 2009-08-27 15:27:05 | Re: BUG #4996: postgres.exe memory consumption keeps going up |