Re: red hat/mysql fiasco

From: Mike Castle <dalgoda(at)ix(dot)netcom(dot)com>
To: General PostgreSQL discussion list <pgsql-general(at)postgresql(dot)org>
Subject: Re: red hat/mysql fiasco
Date: 2000-12-21 15:50:27
Message-ID: 20001221095027.A5037@thune.mrc-home.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 21, 2000 at 11:46:33AM +0200, Alessio Bragadini wrote:
> "The MySQL packages shipped with Red Hat Linux 7 contained buggy
> assembler code. When compiled with optimization
> enabled, this code caused the database server to return bad results.

> P.S. RedHat chose to ship a beta version of MySql with RH7, so I believe
> that's more their fault than MySql people - but indeed there must be
> also a serious flaw in source code.

I would tend to think this would be a bug in gcc.

For instance, gcc (2.95.2 at least) produces buggy code involving "long
long int" under certain circumstances. Sure hope PostgreSQL doesn't use
"long long int" anywhere. Or someone might say that's a serious flaw in
the source code that gcc generated buggy assembler code.

[Actually, the beta version of the gcc compiler that RH is now shipping
with doesn't have this particular long long bug, but the latest official
release of gcc does.]

mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda(at)ix(dot)netcom(dot)com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-12-21 16:03:12 Re: 7.1 Beta 1 & table size calculation
Previous Message Andrew Gould 2000-12-21 15:46:35 RE: Off topic? - Solution for a delimiter problem