mariadb/mysql-test
Marko Mäkelä d0ef1aaf61 MDEV-12123 Page contains nonzero PAGE_MAX_TRX_ID
When MDEV-6076 repurposed the field PAGE_MAX_TRX_ID, it was assumed
that the field always was 0 in the clustered index of old data files.
This was not the case in IMPORT TABLESPACE (introduced in MySQL 5.6
and MariaDB 10.0), which is writing the transaction ID to all index
pages, including clustered index pages.

This means that on a data file that was at some point of its life
IMPORTed to an InnoDB instance, MariaDB 10.2.4 or later could interpret
the transaction ID as a persistent AUTO_INCREMENT value.

This also means that future changes that repurpose PAGE_MAX_TRX_ID
in the clustered index may cause trouble with files that were imported
at some point of their life.

There is a separate minor issue that InnoDB is writing PAGE_MAX_TRX_ID
to every secondary index page, even though it is only needed on leaf
pages. From now on we will write PAGE_MAX_TRX_ID as 0 to non-leaf pages,
just to be able to keep stricter debug assertions.

btr_root_raise_and_insert(): Reset the PAGE_MAX_TRX_ID field on non-root
pages of the clustered index, and on the no-longer-leaf root page of
secondary indexes.

AbstractCallback::is_root_page(): Remove. Use page_is_root() instead.

PageConverter::update_index_page(): Reset the PAGE_MAX_TRX_ID to 0
on other pages than the clustered index root page or secondary index
leaf pages.
2017-04-19 07:59:24 +03:00
..
collections Enable MariaRocks test on Buildbot 2017-04-02 17:29:04 +00:00
extra search_pattern_in_file.inc changes 2017-03-31 19:28:58 +02:00
include MDEV-12424: binlog_encryption.encrypted_* tests fail with Can't locate autodie.pm error 2017-04-02 12:18:23 +03:00
lib use log-error in mtr, don't let mysqld to write to stderr 2017-04-07 09:55:54 +02:00
r MDEV-10355 Weird error message upon CREATE TABLE with DEFAULT 2017-04-18 17:36:05 -07:00
std_data Merge branch '10.1' into 10.2 2017-02-10 17:01:45 +01:00
suite MDEV-12123 Page contains nonzero PAGE_MAX_TRX_ID 2017-04-19 07:59:24 +03:00
t MDEV-10355 Weird error message upon CREATE TABLE with DEFAULT 2017-04-18 17:36:05 -07:00
CMakeLists.txt
dgcov.pl dgcov: import, rewrite to work with cmake and git 2017-01-11 09:18:36 +02:00
disabled.def Move disabled galera tests to galera/disabled.def 2016-11-03 19:30:02 -04:00
mtr.out-of-source
mysql-stress-test.pl
mysql-test-run.pl use log-error in mtr, don't let mysqld to write to stderr 2017-04-07 09:55:54 +02:00
purify.supp
README Updated mysql-test/README with information about KB 2017-01-11 09:19:45 +02:00
README-gcov Fixes for running with gcov 2017-01-11 09:18:35 +02:00
README.stress
suite.pm Extend the innodb.log_corruption test. 2017-02-02 10:20:22 +02:00
unstable-tests Updated list of unstable tests for 10.1.22 2017-03-11 20:59:52 +02:00
valgrind.supp Merge branch '10.1' into 10.2 2017-03-30 12:48:42 +02:00

This directory contains a test suite for the MySQL daemon. To run
the currently existing test cases, simply execute ./mysql-test-run in
this directory. It will fire up the newly built mysqld and test it.

Note that you do not have to have to do "make install", and you could
actually have a co-existing MySQL installation. The tests will not
conflict with it. To run the test suite in a source directory, you
must do make first.

All tests must pass. If one or more of them fail on your system, please
read the following manual section for instructions on how to report the
problem:

https://mariadb.com/kb/en/reporting-bugs

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern socket=/tmp/mysql.sock alias analyze

To match your setup, you might also need to provide --socket, --user, and
other relevant options.

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.

You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

 xemacs t/test_case_name.test

 In the file, put a set of SQL statements that create some tables,
 load test data, and run some queries to manipulate it.

 We would appreciate it if you name your test tables t1, t2, t3 ... (to not
 conflict too much with existing tables).

 Your test should begin by dropping the tables you are going to create and
 end by dropping them again.  This ensures that you can run the test over
 and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case, you should create the result file as follows:

 mysql-test-run --record test_case_name

 or

 mysqltest --record < t/test_case_name.test

 If you only have a simple test cases consisting of SQL statements and
 comments, you can create the test case in one of the following ways:

 mysql-test-run --record test_case_name

 mysql test < t/test_case_name.test > r/test_case_name.result

 mysqltest --record --database test --result-file=r/test_case_name.result < t/test_case_name.test

 When this is done, take a look at r/test_case_name.result
 - If the result is incorrect, you have found a bug. In this case, you should
   edit the test result to the correct results so that we can verify
   that the bug is corrected in future releases.

If you want to submit your test case you can send it 
to maria-developers@lists.launchpad.com or attach it to a bug report on
http://mariadb.org/jira/.

If the test case is really big or if it contains 'not public' data,
then put your .test file and .result file(s) into a tar.gz archive,
add a README that explains the problem, ftp the archive to
ftp://ftp.askmonty.org/private and submit a report to
http://mariadb.org/jira about it.

The latest information about mysql-test-run can be found at:
https://mariadb.com/kb/en/mariadb/mysqltest/

If you want to create .rdiff files, check
https://mariadb.com/kb/en/mariadb/mysql-test-auxiliary-files/