Re: Two weeks to feature freeze

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Dann Corbit <DCorbit(at)connx(dot)com>, Jason Earl <jason(dot)earl(at)simplot(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Two weeks to feature freeze
Date: 2003-06-23 12:46:11
Message-ID: Pine.LNX.4.33.0306230643100.23602-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 21 Jun 2003, Christopher Kings-Lynne wrote:

> Crash-me has nothing to do with testing, it jsut checks to see what
> features a db supports:

An interesting point is that until recently, crashme said that the
postgresql backend crashed on very large queries. The actual problem was
that postgresql has NO LIMIT to query size, and the crashme script would
keep feeding the postgresql backend larger and larger amounts of query
until the internal buffer of the crashme script overran.

This failure was attributed to postgresql when it was, in fact a bug in
the crashme script.

This is not an isolated behaviour of crashme. It's a quick dirty hack job
designed to show the differences between MySQL and all the other
databases. If it was truly comprehensive (i.e. SQL92 spec testing) there
would be hundreds of failure points for MySQL. but it isn't. It tests
only those things that are good in MySQL against other databases (for the
most part, there is some token effort at including a few things MySQL
doesn't do).

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message scott.marlowe 2003-06-23 13:25:56 Re: Two weeks to feature freeze
Previous Message The Hermit Hacker 2003-06-23 12:40:57 Re: informatoin reagarding the last date of submission