mariadb

Tree: b12e8d9095

Author	SHA1	Message	Date
Monty	b12e8d9095	MENT-2235 Aria engine: log initialization failed Some thing causes the aria_log_control file to be larger than the expected 52 bytes. The control file has the correct information but somehow it is filled up with ox00 bytes up to 512 bytes. This could have happened in case of a file system crash that enlarged the file to the sector boundary. Fixed that aria will ignore bytes outside of it's expected Other things: - Fixed wrong DBUG_ASSERT() in my_malloc_size_cb_func() that could cause crashes in debug binaries during Aria recovery.	8 months ago
Monty	1331c73243	Moved server_threads.erase(thd) to end of handle_slave_sql() The effect is that 'show processlist' will show the Slave SQL thread until the thread ends. This may help finding cases where the Slave SQL thread could hang for some time during the cleanup part. The Slave SQL thread will have the state "Slave SQL thread ending' during this stage. Reviewed-by: Kristian Nielsen <knielsen@knielsen-hq.org>	8 months ago
Monty	cc4d9200c4	MDEV-33813 ERROR 1021 (HY000): Disk full (./org/test1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") The problem with MariaDB waiting was fixed earlier. However the server still gives the old error,in case of disk full, that includes "waiting for someone to free some space" even if there is now wait. This commit changes the error message for the non waiting case to: Disk got full writing 'db.table' (Errcode: 28 "No space left on device") Disk got full writing 'test.t1' (Errcode: 28 "No space left on device")Disk got full writing 'test.t1' (Errcode: 28 "No space left on device")Disk got full writing 'test.t1' (Errcode: 28 "No space left on device")	8 months ago
Julius Goryavsky	15139c88a8	Merge branch '10.5' into '10.6'	8 months ago
Julius Goryavsky	3a4c0295ae	galera: synchronization between branches and editions	8 months ago
Oleksandr Byelkin	7544fd4cae	fix problem of reallocated string	8 months ago
Julius Goryavsky	3deac2ea77	galera_inject_bf_log_wait mtr test: more stable test Added explicit checkpoint wait instead of implicit assumption that statement sent via --send will already be executed when lock-contesting statement is started in another session.	8 months ago
Daniel Black	e95a8f84de	MDEV-36156: MSAN Compile and Link flags needed for compile/run checks When MSAN adds the -fsantize=memory this significantly affects compile and link tests. Whether this is a compile/run/or looking for a symbol in a library these cmake tests require the same flags be set. Ideally the minimum invocation of cmake to create a MSAN build as investigated in MDBF-793 should be: -DWITH_MSAN=ON \ -DCMAKE_{EXE,MODULE}_LINKER_FLAGS="-L${MSAN_LIBDIR} -Wl,-rpath=${MSAN_LIBDIR}" On the assumption that the compiler supports msan and the instrumented libraries are in MSAN_LIBDIR (maybe later can be made a cmake option). Without cmake policy below, the checking of everything from libc++ to libfmt will not have the supplied linker flags or the compile options that WITH_MSAN=ON invokes. Many try_compile and CMake functions that wrapped this and headers failed to be recognised due to missing msan symbols when linking. Also without the -L path, they where applying a link test to the default path libraries rather than the MSAN instrumented ones. The CMake policy enabled is CMP0056, added CMake 3.2, applies CMAKE_EXE_LINKER_FLAGS to try_compile. With this change the MY_CHECK_AND_SET_COMPILER_FLAG remove explict build types resulting in just CMAKE_{C,CXX}_FLAGS being set rather than CMAKE_{C,CXX}_FLAGS_{DEBUG,RELWITHDEBINFO}. These are needed for the default CMP0066 policy to be correctly applied and the msan flags of -fsanitizer=memory are applied to all compile checks. Likewise with MY_CHECK_AND_SET_LINKER_FLAG for CMAKE_{EXE,MODULE,SHARED}_LINKER_FLAGS for those check that involve full linking and CHECK_CXX_SOURCE_RUNS for example.	8 months ago
Yuchen Pei	7bb0885397	fixup of MDEV-35959	8 months ago
Julius Goryavsky	e3d7d5ca26	Merge branch '10.5' into '10.6'	8 months ago
Julius Goryavsky	04d731b6cc	galera mtr tests: synchronization between versions Added fixes to galera tests for issues found during merging changes from 10.5 to 10.6.	8 months ago
Yuchen Pei	92d5882ffd	MDEV-35807 Case-insensitive wrappers in spider Continued on the work in MDEV-32157 `18990f0073`	9 months ago
Yuchen Pei	71244c30a1	MDEV-35807 Removed an unused function spider_cmp_trx_alter_table	9 months ago
Yuchen Pei	fcfb89a897	MDEV-35874 Spider: add missing skips when fetching results In MDEV-26345 `77ed235d50` a bitmap is introduced to skip spider GBH SELECTed constant fields when storing the results from the data node. Unfortunately this bitmap was not used in all applicable calls. This patch fixes it. The test covers most of the calls, with the exception of spider_db_store_result_for_reuse_cursor(), which is not covered in existing tests, because it is only called when limit_mode()==1, which is not the case for any spider backend wrapper.	8 months ago
Yuchen Pei	0fa141ebb4	MDEV-36138 Server null-pointer crash at startup when tmptables left in --tmpdir Fix a regression introduced in MDEV-35840 `78157c4765` Also tested compiling with -O3 that the -Warray-bounds fixed in MDEV-35840 does not resurface	8 months ago
Aryan Arora	f3687ccaaf	MDEV-27126 my_getopt compares option names case sensitively my_getopt compares option names case-sensitively, causing "Unknown option" errors when users type mixed-case options like wsrep_slave_UK_checks in lowercase wsrep_slave_fk_checks. Made the comparison in the getopt_compare_strings() case-insensitive.	8 months ago
Monty	bac2358c9d	Removed outdated code comment	8 months ago
Kristian Nielsen	a20c8fabe7	Fix sporadic failure of rpl.rpl_parallel_innodb_lock_conflict Make sure the table mysql.gtid_slave_pos is altered to InnoDB before starting parallel replication. The parallel replication of the suppression insertion in the test case was trying to update the GTID position in parallel with the ALTER TABLE, which could occasionally deadlock on the MDL lock. Reviewed-by: Monty <monty@mariadb.org> Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>	8 months ago
Jan Lindström	b167730499	MDEV-34891 : SST failure occurs when gtid_strict_mode is enabled Problem was that initial GTID was set on wsrep_before_prepare out-of-order. In practice GTID was set to same as previous executed transaction GTID. In recovery valid GTID was found from prepared transaction and this transaction is committed leading to fact that same GTID was executed twice. This is fixed by setting invalid GTID at wsrep_before_prepare and later in wsrep_before_commit actual correct GTID is set and this setting is done while we are in commit monitor i.e. assigment is done in order of replication. In recovery if prepared transaction is found we check its GTID, if it is invalid transaction will be rolled back and if it is valid it will be committed. Initialize gtid seqno from recovered seqno when bootstrapping a new cluster. Added two test cases for both mariabackup and rsync SST methods to show that GTIDs remain consistent on cluster and that all expected rows are in the table. Added tests for wsrep GTID recovery with binlog on and off. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	10 months ago
Marko Mäkelä	5ebff6e15a	MDEV-36038 ALTER TABLE…SEQUENCE does not work correctly with InnoDB mysql_alter_table(): Consider ha_sequence::storage_ht() when determining if the storage engine changed. ha_sequence::check_if_supported_inplace_alter(): A new function, to ensure that ha_innobase::check_if_supported_inplace_alter() will be called on ALTER TABLE name_of_sequence SEQUENCE=0. ha_innobase::check_if_supported_inplace_alter(): For any change of the SEQUENCE attribute, always return HA_ALTER_INPLACE_NOT_SUPPORTED, forcing ALGORITHM=COPY.	8 months ago
Jan Lindström	94ef07d61e	MDEV-32631 : galera_2_cluster: before_rollback(): Assertion `0' failed Test case changes only. Add wait_conditions to make sure nodes rejoin the cluster. Assertion itself should not be possible anymore as we do not allow sequences on Aria tables. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	1 year ago
Marko Mäkelä	f1d7e0c17e	MDEV-35436 dict_stats_fetch_from_ps() unnecessarily holds exclusive dict_sys.latch dict_stats_fetch_from_ps(): Acquire dict_sys.latch as few times as possible, and release dict_sys.latch after invoking pars_sql(), so that we will not be unnecessarily holding dict_sys.latch while possibly waiting for data to be read into the buffer pool.	8 months ago
Marko Mäkelä	7587b0ec84	MDEV-36061 Incorrect error handling on DDL with FULLTEXT INDEX row_create_index_for_mysql(): Tolerate DB_LOCK_TABLE_FULL better. fts_create_one_common_table(), fts_create_one_index_table(): Do not corrupt the error state of a non-active transaction object. fts_config_set_value(): Only run another statement if there was no error yet.	8 months ago
Marko Mäkelä	c07e355c40	MDEV-36015: unrepresentable value in row_parse_int() row_parse_int(): Refactor the code and define the function static in one compilation unit. For any negative values, we must return 0. row_search_get_max_rec(), row_search_max_autoinc(): Moved to the same compilation unit with row_parse_int(). We also remove a work-around of an internal compiler error when targeting ARMv8 on GCC 4.8.5, a compiler that is no longer supported. Reviewed by: Debarun Banerjee	8 months ago
Julius Goryavsky	573b584eba	galera mtr tests: unification of wsrep provider settings	8 months ago
Jan Lindström	bb64a51037	MDEV-35941 : galera_bf_abort_lock_table fails with wait for metadata lock Problem was missing case from wsrep_handle_mdl_conflict. Test case was trying to confirm that LOCK TABLE thread is not BF-aborted. However as case was missing it was BF-aborted. Test case passed because BF-aborting takes time and used wait condition might see expected thread status before it was BF-aborted. Test naturally failed if BF-aborting was done early enough. Fix is to add missing case for SQLCOM_LOCK_TABLES to wsrep_handle_mdl_conflict. Note that using LOCK TABLE is still not recomended on cluster because it could cause cluster hang. This is a 10.5 specific commit that will then be overridden by another one for 10.6+. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	8 months ago
Julius Goryavsky	7b040e53cc	galera mtr tests: fixes for test failures, 'cosmetic' changes and unification between versions	9 months ago
Julius Goryavsky	c35b6f133a	galera mtr tests: synchronization between editions/branches (10.5)	9 months ago
Teemu Ollakka	1b146e8220	galera fix: Donor in non-Primary causes assertion in wsrep-lib Constructed a test which makes donor to go into non-Primary configuration before `sst_sent()` is called, causing an assertion in wsrep-lib if the bug is present. Updated wsrep-lib to version which contains the fix. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	3 years ago
Julius Goryavsky	dd5dc92a19	galera_sequences test: post-fix after MDEV-33245	9 months ago
Julius Goryavsky	eb1811c2ce	galera: disable problematic test (galera_vote_rejoin_dml)	9 months ago
Julius Goryavsky	1456d9ea0a	galera: disable problematic test (MW-329)	9 months ago
Julius Goryavsky	a382b695d2	galera: disable problematic test (galera_vote_rejoin_ddl)	9 months ago
Julius Goryavsky	a7e59c8a54	galera mtr tests: remove unused .result file	9 months ago
Julius Goryavsky	96040fbd53	galera: correction for MENT-2042 test Removed major part of test because XA transactions are not supported in galera on 10.5 branch.	9 months ago
Julius Goryavsky	c9a6adba1e	galera mtr tests: synchronization of tests between branches	2 years ago
Julius Goryavsky	65545a3df2	galera: root certificate renewed	2 years ago
Jan Lindström	c43d0a015f	MDEV-35951 : Complete freeze during MW-329 test Rewrite test not to use infinite procedure, it is not necessary to test. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	9 months ago
Julius Goryavsky	44e1f7238a	MDEV-35941 addendum: additional corrections for mtr tests	8 months ago
Jan Lindström	3009b5439d	MDEV-35941 : galera_bf_abort_lock_table fails with wait for metadata lock Problem was missing case from wsrep_handle_mdl_conflict. Test case was trying to confirm that LOCK TABLE thread is not BF-aborted. However as case was missing it was BF-aborted. Test case passed because BF-aborting takes time and used wait condition might see expected thread status before it was BF-aborted. Test naturally failed if BF-aborting was done early enough. Fix is to add missing case for SQLCOM_LOCK_TABLES to wsrep_handle_mdl_conflict. Note that using LOCK TABLE is still not recomended on cluster because it could cause cluster hang. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	8 months ago
Marko Mäkelä	feadfd9d9c	MDEV-27769 fixup: conditionally define a function	8 months ago
Sergei Golubchik	cd7513995d	MDEV-36026 Problem with INSERT SELECT on NOT NULL columns while having BEFORE UPDATE trigger MDEV-8605 and MDEV-19761 didn't handle INSERT (columns) SELECT followup for `a69da0c31e`	8 months ago
Dave Gosselin	fbb6b50499	MDEV-35117 Improve error message on unexpected geometries for st_distance_sphere When invoking st_distance_sphere with unexpected geometries, the error message now given is: ERROR HY000: Internal error: Point or multipoint geometries expected This commit fixes a few formatting issues in the affected function.	10 months ago
Vlad Lesin	6e6fcf4d43	MDEV-34489 innodb.innodb_row_lock_time_ms fails The test fails trying to compare (innodb/lock)_row_lock_time_avg with some limit. We can't predict (innodb/lock)_row_lock_time_avg value, because it's counted as the whole waiting time divided by the amount of waits. Both waiting time and amount of waits depend on the previous tests execution. The corresponding counters in lock_sys can't be reset with any query. Remove (innodb/lock)_row_lock_time_avg comparision from the test. information_schema.global_status.innodb_row_lock_time can't be reset, compare its difference instead of absolute value. Reviewed by: Marko Mäkelä	9 months ago
Daniel Bartholomew	64b964e757	bump the VERSION	9 months ago
Daniel Bartholomew	3a1f9dfda9	bump the VERSION	9 months ago
Yuchen Pei	0ca98e834d	MDEV-35959 Store the error message at the net layer when reading a packet from the server This ensures that the error message is populated when the reading fails with ER_NET_READ_INTERRUPTED, which at the client layer returns without storing any error message as there is no corresponding CR_ error code. Patch originally by Sergei Golubchik <serg@mariadb.com>	9 months ago
Alexander Barkov	583b39811c	MDEV-35620 UBSAN: runtime error: applying zero offset to null pointer in _ma_unique_hash, skip_trailing_space, my_hash_sort_mb_nopad_bin and my_strnncollsp_utf8mb4_bin UBSAN detected the nullptr-with-offset in a few places when handling empty blobs. Fix: - Adding DBUG_ASSERT(source_string) into all hash_sort() implementations to catch this problem in non-UBSAN debug builds. - Fixing mi_unique_hash(), mi_unique_comp(), _ma_unique_hash(), _ma_unique_comp() to replace NULL pointer to an empty string ponter.. Note, we should also add DBUG_ASSERT(source_string != NULL) into all implementations of strnncoll*(). But I'm afraid the patch is going to be too long and too dangerous for 10.5.	9 months ago
Julius Goryavsky	d6f31ed263	Merge branch '10.5' into '10.6'	9 months ago
Jan Lindström	1f93aece3d	MDEV-24485 : galera.galera_bf_kill_debug MTR failed: A long semaphore wait Test sends a signal to debug_sync and in next command resets debug_sync signals. There is small possibility that sended signal is not yet handled in receiving thread and reset will destroy it causing sync wait timeout. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	12 months ago

1 2 3 4 5 ...

199324 Commits (b12e8d90955179f43bc0c4aa46c3e4d0522fb603) All Branches Search

199324 Commits (b12e8d90955179f43bc0c4aa46c3e4d0522fb603)

All Branches