mlw <markw(at)mohawksoft(dot)com> writes:
> Perhaps we can create a substantial test database? (Millions of records,
> many tables, and a number of relations.) So when we see a problem, we
> can all see it right away. I like "real world" data, because it is often
> more organic than randomized test data, and brings out more issues.
That's true, but a single test database strikes me as the wrong way
to go. The real-life examples that people throw at Postgres are so
varied that a test database could never hope to be an adequate
substitute. I think a test database would likely be subject to
"benchmark syndrome", ie it'd encourage us to optimize with blinders on.
The regression database is actually sufficient to reproduce most simpler
sorts of performance problems, once you know what to look for.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-12-20 19:50:34|
|Subject: Re: Three types of functions, ala function redux. |
|Previous:||From: Tom Lane||Date: 2000-12-20 19:28:01|
|Subject: Re: Is PQreset() proper ? |