News for hackers. Stuff that matters.

A comment on MySQL Doesn’t Always Suck; This Time it’s AMD. Parent comment

Re:MySQL Doesn’t Always Suck; This Time it’s AMD by silentbicycle on Monday April 06, 2009 @04:29PM (#549558)
First of all, this was on OpenSolaris; I don't think it uses RPM packages at all.

Beyond just not crashing, any good database will already have a LOT of code dedicated to verifying data consistency. The best thing MySQL can do in that situation is loudly warn about running on known buggy hardware and then continue checking that its data hasn't been corrupted.

[ Parent | on HN ]
Re:MySQL Doesn’t Always Suck; This Time it’s AMD by jmillikin on Monday April 06, 2009 @05:48PM (#549735)
The MySQL bug report is for x64 Linux. OpenSolaris is used as an example of where AMD's bug has been detected and worked around.
[ Parent | on HN ]
Re:MySQL Doesn’t Always Suck; This Time it’s AMD by silentbicycle on Monday April 06, 2009 @09:27PM (#550061)
I must have misread, sorry.
[ Parent | on HN ]
Re:MySQL Doesn’t Always Suck; This Time it’s AMD by teej on Monday April 06, 2009 @05:14PM (#549647)
MySQL didn't need to do the best thing, it needed to NOT do nothing.
[ Parent | on HN ]
Re:MySQL Doesn’t Always Suck; This Time it’s AMD by silentbicycle on Monday April 06, 2009 @05:25PM (#549683)
Indeed.
[ Parent | on HN ]
Re:MySQL Doesn’t Always Suck; This Time it’s AMD by elijahbuck on Monday April 06, 2009 @09:29PM (#550065)
And that's what it did. As the article said, an assertion failed and the application died (instead of silently corrupting your data).
[ Parent | on HN ]