8 messages in com.mysql.lists.bugsAW: AW: show open tables
FromSent OnAttachments
Christian Rabe05 Jul 2001 13:13 
Sasha Pachev05 Jul 2001 14:05 
Christian Rabe06 Jul 2001 01:45 
Christian Rabe06 Jul 2001 07:16.gz
Michael Widenius06 Jul 2001 08:15 
Christian Rabe06 Jul 2001 08:42 
Sasha Pachev06 Jul 2001 13:09 
Michael Widenius06 Jul 2001 22:02 
Subject:AW: AW: show open tables
From:Christian Rabe (Mave@wallstreet-online.de)
Date:07/06/2001 08:42:50 AM
List:com.mysql.lists.bugs

I meant "show open tables" of course :)

-----Ursprungliche Nachricht----- Von: Christian Rabe [mailto:Mave@wallstreet-online.de] Gesendet: Freitag, 6. Juli 2001 16:17 An: mon@mysql.com Cc: bu@lists.mysql.com Betreff: AW: AW: show open tables

Attached is the gzipped tracefile

I made the following step: - start mysqld - start mysql - execute "show open query" (got unknown error here) - close mysql

Hope that helps.

Christian

-----Ursprungliche Nachricht----- Von: Michael Widenius [mailto:mon@mysql.com] Gesendet: Freitag, 6. Juli 2001 17:15 An: Christian Rabe Cc: bu@lists.mysql.com Betreff: AW: AW: show open tables

Hi!

"Christian" == Christian Rabe <Mave@wallstreet-online.de> writes:

simply take a server that is doing nothing, make a "flush tables" and Christian> after that a "show open tables".

As soon as I make a select or any other operation that touches a table, Christian> no error occures.

Just tried - nothing bad happened. Please make sure to test your test case against a clean lone installation of MySQL that nobody else is connecting Christian> to. Otherwise, you may possibly be omitting critical details without which we Christian> may not be able to repeat the crash.

Christian> That's exactly what I do :) There is only one (my) connection. Christian> Attached is my "doit" script that I use to generate mysql4. Perhaps there is Christian> something "bad" in it. Christian> Also attached is what I get running the test-suite.

Christian> The system is RH7.0 with kernel 2.4.3.

Any change you could download the MySQL source, compile this with --with-debug and make a trace file of this (with mysqld --debug)

Having a trace file should enable us to find out what's wrong quite quickly.

Regards, Monty

PS: I tried to repeat this with MySQL 3.23.39, but everything worked fine for me!