mariadb

Tree: 5eae8c2742

Author	SHA1	Message	Date
Daniel Black	36810342d5	Merge branch '10.3' into 10.4	5 years ago
Daniel Black	3e2afcb3f4	Merge remote-tracking branch 'origin/10.2' into 10.3	5 years ago
Daniel Black	577c970c52	MDEV-24728: Debian include client caching_sha2_password plugin Backport of `4bc31a904f` Include client libraries for auth caching_sha2_password and sha256_password in the libmariadb3 client library package.	5 years ago
Daniel Black	e0ba68ba34	MDEV-23510: arm64 lf_hash alignment of pointers Like the 10.2 version `1635686b50`, except C++ on internal functions for my_assume_aligned. volatile != atomic. volatile has no memory barrier schemantics, its for mmaped IO so lets allow some optimizer gains and stop pretending it helps with memory atomicity. The MDEV lists a SEGV an assumption is made that an address was partially read. As C packs structs strictly in order and on arm64 the cache line size is 128 bits. A pointer (link - 64 bits), followed by a hashnr (uint32 - 32 bits), leaves the following key (uchar * 64 bits), neither naturally aligned to any pointer and worse, split across a cache line which is the processors view of an atomic reservation of memory. lf_dynarray_lvalue is assumed to return a 64 bit aligned address. As a solution move the 32bit hashnr to the end so we don't get the *key pointer split across two cache lines. Tested by: Krunal Bauskar Reviewer: Marko Mäkelä	5 years ago
Daniel Black	1635686b50	MDEV-23510: arm64 lf_hash alignment of pointers volatile != atomic. volatile has no memory barrier schemantics, its for mmaped IO so lets allow some optimizer gains and stop pretending it helps with memory atomicity. The MDEV lists a SEGV an assumption is made that an address was partially read. As C packs structs strictly in order and on arm64 the cache line size is 128 bits. A pointer (link - 64 bits), followed by a hashnr (uint32 - 32 bits), leaves the following key (uchar * 64 bits), neither naturally aligned to any pointer and worse, split across a cache line which is the processors view of an atomic reservation of memory. lf_dynarray_lvalue is assumed to return a 64 bit aligned address. As a solution move the 32bit hashnr to the end so we don't get the *key pointer split across two cache lines. Tested by: Krunal Bauskar Reviewer: Marko Mäkelä	5 years ago
Igor Babaev	bf6484e7bb	MDEV-24910 Crash with SELECT that uses table value constructor as a subselect This bug caused crashes of the server when processing queries with table value constructors (TVC) that contained subqueries and were used itself as subselects. For such TVCs the following transformation is applied at the prepare stage: VALUES (v1), ... (vn) => SELECT * FROM (VALUES (v1), ... (vn)) tvc_x. This transformation allows to reduce the problem of evaluation of TVCs used as subselects to the problem of evaluation of regular subselects. The transformation is implemented in the wrap_tvc(). The code the function to mimic the behaviour of the parser when processing the result of the transformation. However this imitation was not free of some flaws. First the function called the method exclude() that completely destroyed the select tree structures below the transformed TVC. Second the function used the procedure mysql_new_select to create st_select_lex nodes for both wrapping select of the transformation and TVC. This also led to constructing of invalid select tree structures. The patch actually re-engineers the code of wrap_tvc(). Approved by Oleksandr Byelkin <sanja@mariadb.com>	5 years ago
Jan Lindström	d1eeb4b839	MDEV-24964 : Heap-buffer-overflow on wsrep_schema.cc ::remove_fragments Problem was that we used heap allocated key using too small array. Fixed by using dynamic memory allocation using actual needed size.	5 years ago
Jan Lindström	f2428b9c24	MDEV-24967 : Signal 11 on ha_innodb.cc::bg_wsrep_kill_trx line 18611 Null poiter reference in case where bf_thd has no trx .e.g. when we have MDL-conflict.	5 years ago
Jan Lindström	cea03285ec	MDEV-24967 : Signal 11 on ha_innodb.cc::bg_wsrep_kill_trx line 18611 Null poiter reference in case where bf_thd has no trx .e.g. when we have MDL-conflict.	5 years ago
Sergei Petrunia	f83e2ecc50	MDEV-24953: 10.5.9 crashes with large IN() list The problem was in and_all_keys(), the code of MDEV-9759 which calculates the new tree weight: First, it didn't take into account the case when (next->next_key_part=tmp) == NULL and dereferenced a NULL pointer when getting tmp->weight. Second, "if (param->alloced_sel_args > SEL_ARG::MAX_SEL_ARGS) break" could leave the loop with incorrect value of weight. Fixed by introducing SEL_ARG::update_weight_locally() and calling it at the end of the function. This allows to avoid caring about all the above cases.	5 years ago
Daniel Black	2628fa2dba	MDEV-20857: perf schema conflict name filename_hash filename_hash is a function from libiberty.a from the system but also an expored name in the perf schema static library. We'll use a different name.	5 years ago
Marko Mäkelä	f159061510	Merge 10.4 into 10.5	5 years ago
Vicențiu Ciorbaru	ad0f0d2b1a	Merge branch '10.3' into 10.4	5 years ago
Vicențiu Ciorbaru	13f0e1e139	Merge branch '10.2' into 10.3	5 years ago
Vicențiu Ciorbaru	9e259d58c2	Remove race condition during `make dist` Introduced by `85828b8f22` This is running 2 git processes in parallel, which, if unlucky can cause either of them to fail with "File already exists" error.	5 years ago
Marko Mäkelä	3c9d03edda	Merge 10.3 into 10.4	5 years ago
Sergei Golubchik	f33e57a9e6	Merge branch '10.4' into 10.5	5 years ago
Sergei Golubchik	245d33db4e	Merge branch 'github/10.4' into 10.4	5 years ago
Robert Bindar	8b77e6c676	MDEV-24114 SHOW CREATE USER doesnt display correct password expiry status Given PASSWORD EXPIRE and PASSWORD EXPIRE [NEVER\|INTERVAL x DAY] are two different mechanisms, SHOW CREATE USER should display all the information required to restore the state of an account which includes both a manual expired state and an automatic policy. The solution proposed here keeps a CREATE USER ... PASSWORD EXPIRE statement and adds an aditional ALTER USER .. PASSWORD EXPIRE [NEVER\|INTERVAL x DAY] when necessary This way a tool can restore almost the complete state of an account as it was before a dump. The only information left still is the value of the password_last_changed column from mysql.global_priv	5 years ago
Marko Mäkelä	69bf55ffb6	Merge 10.2 into 10.3	5 years ago
Sergei Golubchik	1a0526e2f2	Merge branch 'bb-10.5-release' into 10.5	5 years ago
Thirunarayanan Balathandayuthapani	787c47586e	MDEV-24913 Assertion !recv_no_log_write in log_write_up_to() - The commit 5fd3c7471e3e0673b50d309567c9747d36f09412(MDEV-24709) resets the recv_no_ibuf_operations in recv_recovery_from_checkpoint_start(), but InnoDB fails to reset the variable recv_no_log_write() during that time and that leads to the assert failure.	5 years ago
Sergei Golubchik	e841957416	Merge branch '10.3' into 10.4	5 years ago
Sergei Golubchik	34fcd726a6	Merge branch 'bb-10.4-release' into 10.4	5 years ago
Monty	640f42311a	MDEV-24929 Server crash in thr_multi_unlock or in get_schema_tables_result This was caused by two different bugs: 1) Information_schema tables where not locked by lock_tables, but get_lock_data() was not filtering these out. This caused a crash when mysql_unlock_some_tables() tried to unlock tables early, including not locked information schema tables. Fixed by not locking SYSTEM_TMP_TABLES 2) In some cases the optimizer will notice that we do not need to read the information_schema tables at all. In this case join_tab->read_record is not set, which caused a crash in get_schema_tables_result() Fixed by ignoring const tables in get_schema_tables_result()	5 years ago
Sergei Golubchik	0ab1e3914c	Merge branch '10.2' into 10.3	5 years ago
Sergei Golubchik	ca126d96f5	Merge branch 'bb-10.3-release' into 10.3	5 years ago
Sergei Golubchik	3c021485c9	fix binlog_xa_recover test 1. wait for the binlog thread to reach the certain state, don't use a debug_sync that's incorrectly placed to detect the state 2. no need to do a (non-deterministic) `show binlog events` to verify what is guaranteed by the directly preceding line	5 years ago
Sergei Golubchik	bb98c6bf44	cleanup: renames, no need to create a new .inc file if it's the whole content of a test anyway.	5 years ago
Sergei Golubchik	7fe351aba4	mtr fixes for old (5.10.1) perl	5 years ago
Sergei Golubchik	77c23c62ae	support for mtr --valgdb add a new "debugger" to mtr, that runs the executable under valgrind in gdb. valgrind pid is auto-detected, but the delay (sleep) and vgdb path are hard-coded for now	5 years ago
Sergei Golubchik	feacc0aaf2	unify mtr handling of debuggers "debugger" is anything that wraps execution of a target binary (mysqld or mysqltest). Currently the list includes: gdb, ddd, dbx, lldb, valgrind, strace, ktrace, rr, devenv, windbg, vsjitdebugger. for every debugger xxx, mtr will recognize four options: --xxx, --boot-xxx, --manual-xxx, --client-xxx. They all support an optional "=string" argument. String being a semicolon-separated list of commands (e.g. for gdb) or one (not semicolon-separated) command line of options (e.g. for valgrind). Or both (e.g. --gdb='-quiet -nh;info files' In embedded both --xxx and --client-xxx work. Functionality changed/removed: * --rr-args is gone * --rr-dir is gone * --manual-debug is gone * --debugger={devenv\|vc\|windbg\|vc_express\|vsjitdebugger} is gone * --strace-option is gone * --stracer={strace\|ktrace} is gone * --valgrind only enables it for the server, not for everything * --valgrind-all is gone * --valgrind-mysqltest is gone * --valgrind-mysqld is gone * --valgrind-options is gone * --valgrind-option is gone * --valgrind-path is gone * --callgrind is gone * one cannot combine --valgrind --gdb anymore * valgrind report doesn't add a fake test line to the output * vc and vcexpress on windows are no longer supported	5 years ago
Sergei Golubchik	3b0b4e614c	cleanup: remove dead code in mtr	5 years ago
Sergei Golubchik	c4f0133444	cleanup: stat tables don't allocate Column_statistics_collected objects that won't be used. minor style fixes (StringBuffer<>, etc)	5 years ago
Sergei Golubchik	06a791aa12	MDEV-23753: SIGSEGV in Column_stat::store_stat_fields only collect persistent stats for columns explicitly listed by the user in the ANALYZE TABLE PERSISTENT FOR COLUMNS (...) clause. The engine can extend table->read_set as much as it wants, it should not affect the collected statistics. Test case from the `3b94309a6c` applies - it used to crash, because ha_partition extended table->read_set after the loop that initialized some objects based on bits in the read_set but before the loop that used these objects based on bits in the read_set.	5 years ago
Sergei Golubchik	caad32ca92	Revert "MDEV-23753: SIGSEGV in Column_stat::store_stat_fields" This reverts the commit `3b94309a6c` but keeps the test Because the fix is a hack that isn't supposed to do anything, and relies on a side-effect of rnd_init inside ha_partition. A different fix is coming up.	5 years ago
Sergei Golubchik	a638f1577a	Merge branch 'bb-10.2-release' into 10.2	5 years ago
Igor Babaev	a5b18613ec	MDEV-24936 EXPLAIN for query based on table value constructor lacks info on used subqueries If a query was based on a table value constructor that contained subqueries then EXPLAIN for such query did not contain any lines explaining the execution plans of the subqueries. This happened because - no optimize() method was called for any subquery used by the table value constructor when EXPLAIN command for the query was processed; - EXPLAIN node created for the table value constructor itself did not assume that some child nodes could be attached to it. Approved by Oleksandr Byelkin <sanja@mariadb.com>	5 years ago
Daniel Bartholomew	6aa909745d	bump the VERSION	5 years ago
Daniel Bartholomew	a49ce0bf93	bump the VERSION	5 years ago
Daniel Bartholomew	7b8dacc488	bump the VERSION	5 years ago
Daniel Bartholomew	85bec9d691	bump the VERSION	5 years ago
Thirunarayanan Balathandayuthapani	d7fc4f5236	MDEV-24863 AHI entries mismatch with the index while reloading the evicted tables. - This is caused by commit `ad6171b91c` (MDEV-22456). InnoDB reloads the evicted table again from dictionary. In that case, AHI entries and current index object mismatches happens. When index object mismatches then InnoDB should drop the page hash AHI entries for the block. In btr_search_drop_page_hash_index(), InnoDB should take exclusive lock on the AHI latch if index is already freed to avoid the freed memory access during buf_pool_resize()	5 years ago
Jan Lindström	374f4c3f8c	Suppress warning on galera_ssl_upgrade test.	5 years ago
Monty	8db5274dce	MDEV-22703 DEFAULT() on a BLOB column can overwrite the default record This can cause crashes when accessing already released memory The issue was the Item_default created a internal field, pointing to share->default_values, to be used with the DEFAULT() function. This does not work for BLOB fields as these are freed at end of query. Fixed by storing BLOB field data inside and area allocated by Item_default_value, like we do for nondeterministic default values.	5 years ago
Sergei Golubchik	3a8ca9096e	Merge branch 'bb-10.4-release' into bb-10.5-release	5 years ago
Sergei Golubchik	53123dfa3e	Merge branch 'bb-10.3-release' into bb-10.4-release	5 years ago
Sergei Golubchik	0d55b020e1	Merge branch 'bb-10.2-release' into bb-10.3-release	5 years ago
Sergei Golubchik	ce3a2a688d	make @@wsrep_provider and @@wsrep_notify_cmd read-only this should simplify run-time cluster management	5 years ago
Marko Mäkelä	93522bc9a9	MDEV-24917 Page cleaner wrongly remains idle commit `a993310593` (MDEV-24537) introduced the regression that the page cleaner will keep sleeping even if there is work to do. innodb_max_dirty_pages_pct_update(): Always wake up the page cleaner on any SET GLOBAL innodb_max_dirty_pages_pct= assignment. buf_flush_page_cleaner(): If innodb_max_dirty_pages_pct is nonzero, consult only that parameter when determining whether there is work to do. Else, consult innodb_max_dirty_pages.	5 years ago

... 3 4 5 6 7 ...

192043 Commits (5eae8c274244aaa98320dda3e686f264e8a447d6) All Branches Search

192043 Commits (5eae8c274244aaa98320dda3e686f264e8a447d6)

All Branches