Bug #17997 | Sles9 EM64T cashes often/32Bit is stable | ||
---|---|---|---|
Submitted: | 6 Mar 2006 22:13 | Modified: | 13 Mar 2006 9:04 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.18 | OS: | Linux (SLES9-64Bit) |
Assigned to: | CPU Architecture: | Any |
[6 Mar 2006 22:13]
[ name withheld ]
[9 Mar 2006 13:36]
Valeriy Kravchuk
Thank you for a problem report. What exact version of our binaries do you use? Send also the EXPLAIN results for the query that tent to crash server on 64-bit.
[11 Mar 2006 12:32]
[ name withheld ]
Version used so far: mysqld Ver 5.0.18-standard for unknown-linux-gnu on x86_64 (MySQL Community Edition - Standard (GPL)) MySQL-client-standard-5.0.18-0.sles9 MySQL-server-standard-5.0.18-0.sles9 MySQL-devel-standard-5.0.18-0.sles9 MySQL-shared-standard-5.0.18-0.sles9 Version used now: mysqld --version: mysql Ver 14.12 Distrib 5.0.18, for pc-linux-gnu (i686) using readline 5.0 MySQL-server-standard-5.0.18-0.sles9 MySQL-devel-standard-5.0.18-0.sles9 MySQL-client-standard-5.0.18-0.sles9 MySQL-shared-standard-5.0.18-0.sles9 Either running on: SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.5-7.252-smp (0). I cannot tell about the "explained" statement now, because our "production server" runs the more stable 32Bit-Version now. And MS-Access's translation of the Query through odbc is not obvious. The initial Query is broken down into many peaces. I'll come back when we find a time slot to switch back to the buggy version and are able to analyse the exact behaviour. Or when a new 64-bit version is released at mysql.com. By writing this, I recognise that there is 5.0.19.
[11 Mar 2006 13:28]
[ name withheld ]
Yepp! Version 5.0.19 seems to solve the issues. I suggest u may close the call. BvK
[13 Mar 2006 9:04]
Valeriy Kravchuk
Closed as the problem seems solved in 5.0.19