Re: Add more regression tests for dbcommands

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Robins Tharakan <tharakan(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add more regression tests for dbcommands
Date: 2013-06-27 14:57:24
Message-ID: 21407.1372345044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 6/26/13 12:17 PM, Tom Lane wrote:
>> (I like to
>> point at mysql's regression tests, which take well over an hour even on
>> fast machines. If lots of tests are so helpful, why is their bug rate
>> no better than ours?)

> Tests are not (primarily) there to prevent bugs.

Really? Pray tell, what do you think they're for? Particularly code
coverage tests, which is what these are?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2013-06-27 15:03:53 Re: Error code returned by lock_timeout
Previous Message Kevin Grittner 2013-06-27 14:56:59 Re: Move unused buffers to freelist