mariadb

Tree: 633417308f

Author	SHA1	Message	Date
Jan Lindström	0784dd32b1	MDEV-29775 : Assertion `0' failed in void Protocol::end_statement() when adding data to the MyISAM table after setting wsrep_mode=replicate_myisam If wsrep_mode=BINLOG_ROW_FORMAT_ONLY wsrep_forced_binlog_format can be DEFAULT (UNSPECIFIED) or ROW. Finally, if wsrep_mode=[REPLICATE_MYISAM\|REPLICATE_ARIA] or wsrep_replicate_myisam=ON we allow wsrep_forced_binlog_format to be [DEFAULT\|ROW]. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	3 years ago
Julius Goryavsky	53c693ec2f	Merge branch '10.5' into '10.6'	9 months ago
Jan Lindström	22414d2ed0	MDEV-27861: Creating partitioned tables should not be allowed with wsrep_osu_method=TOI and wsrep_strict_ddl=ON Problem was incorrect handling of partitioned tables, because db_type == DB_TYPE_PARTITION_DB wsrep_should_replicate_ddl incorrectly marked DDL as not replicatable. However, in partitioned tables we should check implementing storage engine from table->file->partition_ht() if available because if partition handler is InnoDB all DDL should be allowed even with wsrep_strict_ddl. For other storage engines DDL should not be allowed and error should be issued. This is 10.5 version of the fix. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	2 years ago
Julius Goryavsky	de216618e2	MDEV-29775 addendum: Relaxation of unnecessary restrictions + cosmetic corrections taken from the 10.6+ branch of the fix (to simplify merge).	1 year ago
Jan Lindström	7d69902d83	MDEV-29775 : Assertion `0' failed in void Protocol::end_statement() when adding data to the MyISAM table after setting wsrep_mode=replicate_myisam If wsrep_replicate_myisam=ON we allow wsrep_forced_binlog_format to be [DEFAULT\|ROW]. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	3 years ago
Jan Lindström	3f5b6a9837	MDEV-35748 : Attempting to create a CONNECT engine Table results in non-InnoDB sequences in Galera cluster error Problem was incorrect condition on wsrep_check_sequence when ENGINE!=InnoDB. Fix is not use DB_TYPE_XXX because it is not correct on dynamic storage engines. Instead used storage engine name is looked from thd->lex->m_sql_cmd->option_storage_engine_name. For CREATE TABLE allow anyting except ENGINE=SEQUENCE. For CREATE SEQUENCE only ENGINE=InnoDB is supported. For ALTER TABLE if original table contains sequence information only ENGINE=InnoDB is supported. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	10 months ago
Brandon Nesterenko	f1276aa1bc	MDEV-26652: xa transactions binlogged in wrong order Disclaimer: This report was fixed in a previous commit with MDEV-21117, this patch only adds a test to show the presence of the fix. Prior to MDEV-21117, the ordering of the handlers in a transaction's ha_info list solely determined the order in which the handlertons commit. The binlog is supposed to commit first, and is normally placed first in the ha_list to do so; however, in multi-engine 2-phase XA transactions, the binlog can be placed second. This allowed a race-condition for other concurrent transactions to commit and binlog before the prior XA COMMIT would be written to binlog. MDEV-21117 fixed this so the binlog is specially considered to commit first, before traversing the ha_list (see commit_one_phase_2() in sql/hander.cc for this specific change in `6c39eaeb12`).	1 year ago
Sergei Golubchik	066e8d6aea	Merge branch '10.5' into 10.6	9 months ago
Sergei Golubchik	a89e734fcb	ColumnStore 6.4.10-1	9 months ago
Sergei Golubchik	d0c2a007ee	C/C 3.3.14	9 months ago
Sergei Golubchik	17e31abd8b	compilation failure on CentOS 7	9 months ago
Sergei Golubchik	38d3b6027b	MDEV-35943 ASAN errors in Query_arena::free_items / fill_schema_table_from_frm shouldn't try to close the table if open failed. followup for `deb20fb751`	9 months ago
Sergei Golubchik	03d2328785	MDEV-35944 DELETE fails to notice transaction abort, violating ACID Process errors of read_record(). Also, add an assert that Marko requested	9 months ago
Marko Mäkelä	d5e7bce14b	MDEV-35966 galera.galera_as_master crashes in debug builds innobase_commit(): When Galera is used with SET SQL_LOG_BIN=OFF, some debug assertions that had been added in commit `ddd7d5d8e3` (MDEV-24035) would fail. Let us relax those assertions for Galera transactions, to allow an implicit commit after an internally executed XA PREPARE. Note that trx_undo_report_row_operation() only allows undo log records to be added to ACTIVE transactions (not after XA PREPARE). Hence, this relaxation should be safe with respect to writes.	9 months ago
Marko Mäkelä	3cfffb4de6	MDEV-35962 CREATE INDEX fails to heal a FOREIGN KEY constraint commit_cache_norebuild(): Replace any newly added indexes in the attached foreign key constraints.	9 months ago
Alexey Botchkov	47908d3f77	MDEV-32619 Fix setting SRID with ST_*FromWKB(). second argument is handled in Item_func_geometry_from_wkb::val_str. contributed by Maximilian Krög <maxi_kroeg@web.de>	9 months ago
Sergei Golubchik	7eded23be6	ColumnStore 5.6.9-1	9 months ago
Sergei Golubchik	1fec4fc4f8	more C API methods in the service_sql for columnstore	3 years ago
Sergei Golubchik	ffff702623	C/C 3.1.27	9 months ago
Sergei Golubchik	fafa10dbc4	update HeidiSQL to 12.10 also, switch to https	9 months ago
Sergei Golubchik	66cf3c6974	MDEV-35612 fix for system-versioning only ignore fully invisible fields	9 months ago
Sergei Golubchik	c1933b46e4	MDEV-33285 make the test deterministic need to clear old signals before waiting for new signals with the same name	9 months ago
Sergei Golubchik	caec03cb79	MDEV-35907 debian-start script fails when using non-standard socket path consistently use --defaults-extra-file for all command-line tools	9 months ago
Sergei Golubchik	9a0ac0cdf7	MDEV-35911 Assertion `marked_for_write_or_computed()' failed in bool Field_new_decimal::store_value(const my_decimal, int) disable the assert. also, use the same check for check_that_all_fields_are_given_values() as it's used in not_null_fields_have_null_values() - to avoid issuing the same warning twice.	9 months ago
Dave Gosselin	b8b77177c2	MDEV-35964 fix cast warnings on mac in mysql_file.h Cast create_flags to mode_t when passing to my_create and my_create_with_symlink	9 months ago
Julius Goryavsky	bcb87f5ccb	fix for galera_query_cache_invalidate test results	9 months ago
Daniele Sciascia	0018df2b55	galera fix: Assertion `WSREP(thd)` failed in wsrep_restore_kill_after_commit() Wsrep_commit_empty happens too early when wsrep is disabled. Let the cleanup happen at end of statement. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	2 years ago
Julius Goryavsky	50d49493db	galera: fixes for mtr test for performance schema	2 years ago
Daniele Sciascia	c43db43a7c	MENT-2038 Assert WSREP(thd) fails in wsrep_restore_kill_after_commit Fix wrong assertion: function wsrep_restore_kill_after_commit() asserts `WSREP(thd)`, however for the caller (wsrep_after_statement()) it is enough that the THD has an active transaction. Fixed the assertion accordingly. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	2 years ago
Julius Goryavsky	479a5832f0	galera fix: MSAN reports use-of-uninitialized-value on binlog_encryption This commit fixes a bug in MSAN verification in debug builds related to the member of a lex->definer structure field that may be uninitialized for some SET statements. The bug is caused by debug output in a wsrep-specific insert and does not affect server functionality.	1 year ago
Julius Goryavsky	862d1be2e6	MDEV-25718 addendum: stabilization of test success (especially for 11.4+) Added DEBUG_SYNC_С("ha_write_row_end") in the WSREP branch, and added a new status to the list of pending statuses in the mtr test.	9 months ago
Julius Goryavsky	779ae4c511	wsrep mtr tests: fix for MDEV-23081 failure Sometimes a database can be created with --log-bin but then the .combinations file causes a switch to start without --log-bin causing a failure on recovery. This commit fixes this issue.	9 months ago
Julius Goryavsky	331975c5c5	galera: disable problematic test (galera_nbo_master_non_prim_failure)	9 months ago
Julius Goryavsky	5af1f69a84	MDEV-26266 addendum: more stable test This test must be performed on newly launched nodes and then a restart must be performed.	9 months ago
Julius Goryavsky	0a5d6cf478	galera: disable problematic test (galera_sequences)	9 months ago
Julius Goryavsky	acf7b000ff	fixes for galera_as_slave replication tests	9 months ago
Jan Lindström	e53ffdee96	MDEV-35804 : galera_ddl_fk_conflict test failed due to timeout Test case changes only. Use better wait_conditions. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	10 months ago
Julius Goryavsky	2cfad396ee	galera tests: more informative messages about the number of variables	9 months ago
Jan Lindström	0ddaefcc76	galera fix : MW-402 galera test fails sporadically Test was using after certification sync point when it was intended to use before certification sync point. This caused sporadic failures. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	11 months ago
Jan Lindström	6e3274e814	MENT-31857 post-fix: fix for timeouts in the galera_as_slave_ctas test Caused by MDEV-31857 enable --ssl-verify-server-cert by default in the internal client. Fixed by disabling master_ssl_verify_server_cert because account is passwordless. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	11 months ago
Hemant Dangi	c0b11e75ff	MDEV-34218: Mariadb Galera cluster fails when replicating from Mysql 5.7 on use of DDL Issue: Mariadb Galera cluster fails to replicate from Mysql 5.7 when configured with MASTER_USE_GTID=no option for CHANGE MASTER. HOST: mysql, mysql 5.7.44 binlog_format=ROW HOST: m1, mariadb 10.6 GALERA NODE replicating from HOST mysql, Using_Gtid: No (log file and position) HOST: m2 mariadb 10.6 GALERA NODE HOST: m3 mariadb 10.6 GALERA NODE Error on m1: 2024-05-22 16:11:07 1 [ERROR] WSREP: Vote 0 (success) on 78cebda7-1876-11ef-896b-8a58fca50d36:2565 is inconsistent with group. Leaving cluster. Error on m2 and m3: 2024-05-22 16:11:06 2 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 42, event_type: -94 2024-05-22 16:11:06 2 [ERROR] WSREP: applier could not read binlog event, seqno: 2565, len: 482 It fails in Gtid_log_event::is_valid() check on secondary node when sequence number sent from primary is 0. On primary for applier or slave thread sequence number is set to 0, when both thd->variables.gtid_seq_no and thd->variables.wsrep_gtid_seq_no have value 0. Solution: Skip adding Gtid Event on primary for applier or slave thread when both thd->variables.gtid_seq_no and thd->variables.wsrep_gtid_seq_no have value 0. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>	10 months ago
Marko Mäkelä	746471b8d8	MDEV-33978 P_S.THREADS is not showing all server threads page_encrypt_thread_key: The key for fil_crypt_thread(). All other InnoDB threads should already have been registered for performance_schema ever since commit `a2f510fccf`	9 months ago
Marko Mäkelä	831f5bc66f	MDEV-33978 P_S.THREADS is not showing all server threads page_encrypt_thread_key: The key for fil_crypt_thread(). All other InnoDB threads should already have been registered for performance_schema ever since commit `a2f510fccf`	9 months ago
Galina Shalygina	dffe3d1fb2	MDEV-35910 Conditions with SP local variables are not pushed into derived table This bug prevented building conditions that could be pushed into a derived table if the derived table was used in a query of a stored procedure and the conditions contained local variables of the procedure. This could lead to a slow execution of the procedure. Also in some cases the bug prevented building conditions that could be pushed from the HAVING condition into the WHERE condition of a query if the conditions to be built used local variables of a stored procedure. To failure to build such pushable conditions was due to lack of a proper implementation of the virtual method to copy items for the objects of the class Item_splocal. Approved by Igor Babaev <igor@mariadb.com> who had to change the original fix that just added the regular copying of the nodes of the Item_splocal class to take into account the wrappers do_get_copy() and do_build_clone() introduced after the fix had been prepared. He also changed the test case to demonstrate that the fix was really needed for pushdown from HAVING into WHERE.	9 months ago
Nikita Malyavin	765458c93c	fix my_error usage	5 years ago
Nikita Malyavin	e7cc1a3047	MDEV-33658 2/2 Cannot add a foreign key on a table with a matching long UNIQUE Cannot add a foreign key on a table with a long UNIQUE multi-column index, that contains a foreign key as a prefix. Check that index algorithms match during the "generated" keys duplicate removal.	1 year ago
Nikita Malyavin	ecaedbe299	MDEV-33658 1/2 Refactoring: extract Key length initialization mysql_prepare_create_table: Extract a Key initialization part that relates to length calculation and long unique index designation. append_system_key_parts call also moves there. Move this initialization before the duplicate elimination. Extract WITHOUT OVERPLAPS check into a separate function. It had to be moved earlier in the code to preserve the order of the error checks, as in the tests.	1 year ago
Nikita Malyavin	e33064e0fc	MDEV-27769 Assertion failed in Field::ptr_in_record upon UPDATE in ORACLE mode table->move_fields has some limitations: 1. It cannot be used in cascade 2. It should always have a restoring pair In this case, an error has occurred before the field ptr was restored, returning from the function in that state. Even in case of an error, the table can be reused afterwards and table->field[i]->ptr is not reset in between. The solution is to restore the field pointers immanently whenever they've been deviated. Also add an assertion that ensures that table fields are restored after the use in close_thread_tables.	9 months ago
Brandon Nesterenko	cb5dd76959	MDEV-35938: rpl.rpl_parallel_gco_wait_kill fails - "Can't initialize replace ..." Test rpl.rpl_parallel_gco_wait_kill has a race condition where it identifies that SQL using its state as "Slave has read all relay log", and immediately tries to save the thread id of the SQL thread by querying for threads with that same state. However, the state of the SQL thread may change in-between this time, leading to the query that saves the SQL thread finding no thread id that matches that state. Commit `3ee6f69d49` aimed to fix this in 10.11+ by simplifying the query string to "%relay log%"; however, it could still fail (though less often). This commit instead changes the query to find the SQL thread from using some state, to using the command "Slave_SQL", which will not change	9 months ago
Oleksandr Byelkin	47f87c5f88	MDEV-20281 "[ERROR] Failed to write to mysql.slow_log:" without error reason Add "backup" (in case of absence issued by error) reasons for failed logging.	9 months ago

... 5 6 7 8 9 ...

199566 Commits (633417308f163141a822398fcf8e7f281bcda38b) All Branches Search

199566 Commits (633417308f163141a822398fcf8e7f281bcda38b)

All Branches