Oracle 5.0, Reference Manual

Page: 151 / 3232

Unix Postinstallation Procedures
131
+---------------------------+
| Tables |
+---------------------------+
| columns_priv |
| db |
| func |
| help_category |
| help_keyword |
| help_relation |
| help_topic |
| host |
| proc |
| procs_priv |
| tables_priv |
| time_zone |
| time_zone_leap_second |
| time_zone_name |
| time_zone_transition |
| time_zone_transition_type |
| user |
+---------------------------+
shell> bin/mysql -e "SELECT Host,Db,User FROM db" mysql
+------+--------+------+
| host | db | user |
+------+--------+------+
| % | test | |
| % | test_% | |
+------+--------+------+
12. There is a benchmark suite in the
sql-bench
directory (under the MySQL installation directory)
that you can use to compare how MySQL performs on different platforms. The benchmark suite is
written in Perl. It requires the Perl DBI module that provides a database-independent interface to
the various databases, and some other additional Perl modules:
DBI
DBD::mysql
Data::Dumper
Data::ShowTable
These modules can be obtained from CPAN ( http://www.cpan.org/ ). See also Section 2.22.1,
“Installing Perl on Unix” .
The
sql-bench/Results
directory contains the results from many runs against different
databases and platforms. To run all tests, execute these commands:
shell> cd sql-bench
shell> perl run-all-tests
If you do not have the
sql-bench
directory, you probably installed MySQL using RPM files
other than the source RPM. (The source RPM includes the
sql-bench
benchmark directory.)
In this case, you must first install the benchmark suite before you can use it. There are separate
benchmark RPM files named
mysql-bench-VERSION.i386.rpm
that contain benchmark code
and data.
If you have a source distribution, there are also tests in its
tests
subdirectory that you can run. For
example, to run
auto_increment.tst
, execute this command from the top-level directory of your
source distribution:
shell> mysql -vvf test < ./tests/auto_increment.tst
The expected result of the test can be found in the
./tests/auto_increment.res
file.
13. At this point, you should have the server running. However, none of the initial MySQL accounts
have a password, and the server permits permissive access to test databases. To tighten security,
follow the instructions in
Section 2.18.2, “Securing the Initial MySQL Accounts” .