Server IP : 172.67.216.182 / Your IP : 162.158.170.123 Web Server : Apache System : Linux krdc-ubuntu-s-2vcpu-4gb-amd-blr1-01.localdomain 5.15.0-142-generic #152-Ubuntu SMP Mon May 19 10:54:31 UTC 2025 x86_64 User : www ( 1000) PHP Version : 7.4.33 Disable Function : passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /www/server/mysql/src/mysql-test/suite/engines/rr_trx/t/ |
Upload File : |
################################################################################ # # This test contains a single transaction performing queries against the test # data. The main purpose is to test REPEATABLE READ results, that is to verify # that reads (SELECTs) are indeed repeatable during a REPEATABLE READ # transaction. # # Generally, queries which should yield the same results at one moment in time # should also yield the same results later in the same transaction. In some # configurations, however, phantom reads are allowed (may e.g. depend on # settings such as falcon_consistent_read). # # To detect missing rows, modified rows and possibly invalid (uncommitted) # extra (phantom) rows, we store query results in temporary tables and compare # using special queries. Using includes for this to avoid unnecessary "clutter" # in each select-only test. # # This and similar tests (transactions) should contain some random "filler" # between the SELECTs so that they may run in different conditions, such as: # * some other transactions may have commited in the meantime # * a scavenge run may have happened (falcon) # * etc # # Such a "random filler" can be: # * SLEEP() # * Bogus updates on some unrelated temporary table that was created for the purpose # * savepoint + bogus updates on the main tables + rollback to savepoint # * Inserts on new records (which will show up as "phantom" records in subsequent SELECTs) # ################################################################################ SET autocommit = 0; START TRANSACTION; # We do a full table scan in this test. # Note: May cause deadlocks! (handled in sourced scripts). let $query= SELECT * from t1; --source suite/engines/rr_trx/include/record_query_all_columns.inc SELECT SLEEP(1); let $query= SELECT * from t1; --source suite/engines/rr_trx/include/record_query_all_columns.inc --source suite/engines/rr_trx/include/check_repeatable_read_all_columns.inc COMMIT;