| Server IP : 185.86.78.101 / Your IP : 216.73.216.124 Web Server : Apache System : Linux 675867-vds-valikoshka1996.gmhost.pp.ua 5.4.0-150-generic #167-Ubuntu SMP Mon May 15 17:35:05 UTC 2023 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 : OFF Directory : /www/server/mysql/mysql-test/t/ |
Upload File : |
--source include/not_gtid_enabled.inc --let $old_server_id= `SELECT @@GLOBAL.server_id` --let $new_server_id= `SELECT $old_server_id + 1` # # BUG#20748502: ASSERTION `THD->VARIABLES.GTID_NEXT.TYPE== ANONYMOUS_GROUP' FAILED. # # This test case verifies that the server does not # assert. The steps to reproduce the assert are: # # 1. set autocommit to zero # 2. create a temporary table - this would raise the # GTID-violation flag # 3. Set GTID_NEXT explicitly # 4. Issue a statement and commit the current # transaction - since GTID_NEXT and GTID-violation are # set then the system will try to decrease the number # of GTID-violation transactions. # SET @@GLOBAL.GTID_MODE=OFF_PERMISSIVE; CREATE TABLE t2 (c1 INT); set @@autocommit=0; CREATE TEMPORARY TABLE t1(a INT key); COMMIT; SET SESSION GTID_NEXT='AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE:1'; # before the patch, this would assert INSERT INTO t2 VALUES(1); COMMIT; SET SESSION GTID_NEXT=AUTOMATIC; DROP TABLE t2; SET GLOBAL GTID_MODE=OFF; # # Bug #20743468: ASSERTION `OLD_VALUE >= 1' FAILED. | ABORT (SIG=6) IN GTID_STATE::END_ANONYMOUS_ # # This test case verifies that the server does not # assert. The steps to reproduce the assert are: # # 1. set autocommit to zero # 2. Issue CREATE TABLE ... SELECT - this would raise the # GTID-violation flag (when it should not if the binlog # is disabled). # 3. Issue a BINLOG statement - this implicitly sets GTID_NEXT # to ANONYMOUS. # 4. Issue a DDL - since GTID_NEXT and GTID-violation are set # then the system will try to decrease the number of # GTID-violation transactions. # needs a valid server id (>=1) --replace_result $new_server_id NEW_SERVER_ID --eval SET GLOBAL server_id= $new_server_id USE test; CREATE TABLE t1 SELECT 1 a; BINLOG ' MfmqTA8BAAAAZwAAAGsAAAABAAQANS41LjctbTMtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAx+apMEzgNAAgAEgAEBAQEEgAAVAAEGggAAAAICAgCAA== '; # this would assert before the patch --disable_warnings DROP FUNCTION IF EXISTS inexistent_function; --enable_warnings DROP TABLE t1; # # One needs to set GTID_NEXT to DEFAULT after the # BINLOG '<fd event>', since it implicitly sets # GTID_NEXT to ANONYMOUS (by design). # SET SESSION GTID_NEXT=DEFAULT; --replace_result $old_server_id OLD_SERVER_ID --eval SET GLOBAL server_id = $old_server_id SET GLOBAL GTID_MODE=OFF;