n about any table in a database
that will help us create a situation matching the one you have
For speed-related bugs or problems with SELECT statements you should
always include the output of EXPLAIN SELECT and at least the
number of rows that the SELECT statement produces The more
information you give about your situation the more likely it is that someone
can help you! For example the following is an example of a very good bug
report (it should of course be posted with the mysqlbug script):
Example run using the mysql command line tool (note the use of the
\G statement terminator for statements whose output width would
otherwise exceed that of an 80-column display device):
mysql> SHOW VARIABLES;
mysql> SHOW COLUMNS FROM \G
<output-from-SHOW-COLUMNS>
mysql> EXPLAIN SELECT \G
<output-from-EXPLAIN>
mysql> FLUSH STATUS;
mysql> SELECT ;
<A short version of the output from SELECT
including the time taken to run the query>
mysql> SHOW STATUS;
<output from SHOW STATUS>
If a bug or problem occurs while running MySQL try to provide an
input script that will reproduce the anomaly This script should include any
necessary source files The more closely the script can reproduce your
situation the better
If you cant provide a script you should at least include the output
from mysqladmin variables extended-status processlist in your mail to
provide some information of how your system is performing!
If you think that MySQL produces a strange result from a query
include not only the result but also your opinion of what the result
should be and an account describing the basis for your opinion
When giving an example of the problem its better to use the variable names
table names etc that exist in your actual situation than to come up with
new names The problem could be related to the name of a variable table
etc! These cases are rare perhaps but it is better to be safe than
sorry After all it should be easier for you to provide an example that
uses your actual situation and it is by all means better for us In case you
have data you dont want to show to others you can use ftp to
transfer it to wwwmysqlcom/pub/mysql/secret/ If the data are
really top secret and you dont want to show them even to us then go ahead
and provide an example using other names but please regard this as the last
choice
Include all the options given to the relevant programs if possible For
example indicate the options that you use when you start the mysqld
daemon and that you use to run any MySQL client programs The
options to programs like mysqld and mysql and to the
configure script are often keys to answers and very relevant! It is
never a bad idea to include them anyway! If you use any modules such as
Perl or PHP please include the version number(s) of those as well
If you cant produce a test case in a few rows or if the test table
is too big to be mailed to the mailing list (more than 10 rows) you should
dump your tables using mysqldump and create a `README file
that describes your problem
Create a compressed archive of your files using
tar and gzip or zip and use ftp
to transfer the archive to wwwmysqlcom/pub/mysql/secret/
Then send a short description of the problem to =mysqllistsmysqlcom>mysqllistsmysqlcom
If your question is related to the privilege system please include the
output of mysqlaccess the output of mysqladmin reload and all
the error messages you get when trying to connect! When you test your
privileges you should first run mysqlaccess After this execute
mysqladmin reload version and last you should try to connect with the
program that gives you trouble mysqlaccess can be found in the
`bin directory under your MySQL installation directory
If you have a patch for a bug that is good But dont assume the patch is
all we need or that we will use it even if you dont provide some necessary
information such as test cases showing the bug that your patch fixes We
might find problems with your patch or we