mariadb

Tree: 217caf27e3

Author	SHA1	Message	Date
Jan Lindström	217caf27e3	Update result files for Galera library 26.4.9	4 years ago
Leandro Pacheco	2b84e1c966	MDEV-23080: desync and pause node on BACKUP STAGE BLOCK_DDL make BACKUP STAGE behave as FTWRL, desyncing and pausing the node to prevent BF threads (appliers) from interfering with blocking stages. This is needed because BF threads don't respect BACKUP MDL locks. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>	4 years ago
Sergei Golubchik	389f5cf76f	disable spider/bugfix.wait_timeout	4 years ago
Sergei Golubchik	8d3d802c54	fix spider/bugfix.delete_with_float_column_mysql --ps as always, multi-commands don't work in --ps	4 years ago
Sergei Golubchik	4533e6ef65	MDEV-18353 Shutdown may miss to wait for connection thread * count CONNECT objects too * wait for all CONNECT objects to disappear (to be converted to THDs) before killing THDs away	4 years ago
Sergei Golubchik	b34cafe9d9	cleanup: move thread_count to THD_count::value() because the name was misleading, it counts not threads, but THDs, and as THD_count is the only way to increment/decrement it, it could as well be declared inside THD_count.	4 years ago
Marko Mäkelä	1fb71c7831	MDEV-19272: Assertion unireg_check..Field::NEXT_NUMBER failed ha_innobase::check_if_supported_inplace_alter(): Relax a too strict debug assertion when changing a column from NULL to NOT NULL. InnoDB actually allows instant removal of an AUTO_INCREMENT attribute since commit `8dffaaef72` (MDEV-12836).	4 years ago
Vladislav Vaintroub	0604592a85	fix ssl_cipher test Setting specific ciphers does not work for OpenSSL 1.1.1+ client when it negotiates TLSv1.3 with the server. Require TLS version less that 1.3 for the server to workaround.	4 years ago
Michael Okoko	6cd3588f0e	Improve documentation of json parser functions Signed-off-by: Michael Okoko <okokomichaels@outlook.com>	4 years ago
Nayuta Yanagisawa	aafb888657	MDEV-26013 distinct not work properly in some cases for spider tables The bug is caused by the following reasons: * spider_group_by_handler::init_scan() generates a query for a data node. * The function adds DISTINCT if and only if spider_group_by_handler::query::distinct is TRUE. * spider_group_by_handler::query::distinct is set to the value of JOIN::select_distinct in JOIN::make_aggr_tables_info(). * In the test case, DISTINCT is not added because JOIN::select_distinct is FALSE at the call of JOIN::make_aggr_tables_info(). Why JOIN::select_distinct is set to FALSE? That is because the function JOIN::optimize_stage2() convert DISTINCT into GROUP BY and then optimizes away GROUP BY.	4 years ago
Vladislav Vaintroub	7ffa801cf2	MDEV-22221 Compile WolfSSL with TLSv1.3 support	4 years ago
Vladislav Vaintroub	6a3e0009a6	WolfSSL 4.8.0	4 years ago
Marko Mäkelä	3e5a11e488	MDEV-25236 fixup: instant_alter_debug,dynamic result We only support the instantaneous removal of the NOT NULL attribute for ROW_FORMAT=REDUNDANT tables.	4 years ago
Sergei Golubchik	7af5d96f00	MDEV-22221: MariaDB with WolfSSL doesn't support AES-GCM cipher for SSL commit the forgotten result file followup for `b81803f065`	4 years ago
Sergei Golubchik	bd3ac6758a	fix perfschema.sizing_* tests to run still cannot be enabled permanently, but at least they could be run manually, if needed	4 years ago
Nayuta Yanagisawa	e3814a74ee	MDEV-26139 Spider crashes with segmentation fault (signal 11) on CREATE TABLE when COMMENT does not contain embedded double quotes The root cause of the bug MDEV-26139 is the lack of NULL checking on the variable `dq`. Comments on if (dq && (!sq \|\| sq > dq)) {...} else {...}: * The if block corresponds to the case where parameters are quoted by double quotes. In that case, a single quote doesn't appear at all or only appears in the middle of double quotes. * The else block corresponds to the case where parameters are quoted by single quotes. In that case, a double quote doesn't appear at all or only appears in the middle of single quotes. * If the program reaches the if-else statement, `sq \|\| dq` holds. Thus, the negation of `dq && (!sq \|\| sq > dq)` is equivalent to `sq && (!dq \|\| sq <= dq)`.	4 years ago
Igor Babaev	78735dcaf7	MDEV-26108 Crash with query referencing twice CTE that uses embedded recursive CTE This bug could affect queries that had at least two references to a CTE that used an embedded recursive CTE. Starting from version 10.4 some code in With_element::clone_parsed_spec() that assumed a certain order of selects after parsing the specification of a CTE became not valid anymore. It could lead to global select lists where some selects were missing. If a missing CTE happened to belong to the recursive part of a recursive CTE some recursive table references were not set as references to materialized derived tables and this caused a crash of the server. Approved by Oleksandr Byelkin <sanja@mariadb.com>	4 years ago
Julius Goryavsky	e56fe39310	MDEV-25978: minor post-merge fix for .result file	4 years ago
Marko Mäkelä	a635588b56	MDEV-25236 Online log apply fails for ROW_FORMAT=REDUNDANT tables In other ROW_FORMAT than REDUNDANT, the InnoDB record header size calculation depends on dict_index_t::n_core_null_bytes. In ROW_FORMAT=REDUNDANT, the record header always is 6 bytes plus n_fields or 2*n_fields bytes, depending on the maximum record size. But, during online ALTER TABLE, the log records in the temporary file always use a format similar to ROW_FORMAT=DYNAMIC, even omitting the 5-byte fixed-length part of the header. While creating a temporary file record for a ROW_FORMAT=REDUNDANT table, InnoDB must refer to dict_index_t::n_nullable. The field dict_index_t::n_core_null_bytes is only valid for other than ROW_FORMAT=REDUNDANT tables. The bug does not affect MariaDB 10.3, because only commit `7a27db778e` (MDEV-15563) allowed an ALGORITHM=INSTANT change of a NOT NULL column to NULL in a ROW_FORMAT=REDUNDANT table. The fix was developed by Thirunarayanan Balathandayuthapani and tested by Matthias Leich. The test case was simplified by me.	4 years ago
Marko Mäkelä	372ea88264	Merge 10.3 into 10.4	4 years ago
Marko Mäkelä	f9194d02da	Merge 10.2 into 10.3	4 years ago
Marko Mäkelä	a6adefad4b	Fixup `586870f9ef` One more result was affected by merging `768c51880a`.	4 years ago
Eugene Kosov	ffe744e77d	submodules.cmake: add missing --depth=1	4 years ago
Marko Mäkelä	c294443b41	Merge 10.3 into 10.4	4 years ago
Marko Mäkelä	05f7fd571f	Merge 10.2 into 10.3	4 years ago
Marko Mäkelä	2bf6f2c054	MDEV-26077 Assertion err != DB_DUPLICATE_KEY or unexpected ER_TABLE_EXISTS_ERROR This is a backport of `161e4bfafd`. trans_rollback_to_savepoint(): Only release metadata locks (MDL) if the storage engines agree, after the changes were already rolled back. Ever since commit `3792693f31` and mysql/mysql-server@55ceedbc3feb911505dcba6cee8080d55ce86dda we used to cheat here and always release MDL if the binlog is disabled. MDL are supposed to prevent race conditions between DML and DDL also when no replication is in use. MDL are supposed to be a superset of InnoDB table locks: InnoDB table lock may only exist if the thread also holds MDL on the table name. In the included test case, ROLLBACK TO SAVEPOINT would wrongly release the MDL on both tables and let ALTER TABLE proceed, even though the DML transaction is actually holding locks on the table. Until commit `1bd681c8b3` (MDEV-25506) in MariaDB 10.6, InnoDB would often work around the locking violation in a blatantly non-ACID way: If locks exist on a table that is being dropped (in this case, actually a partition of a table that is being rebuilt by ALTER TABLE), InnoDB could move the table (or partition) into a queue, to be dropped after the locks and references had been released. If the lock is not released and the original copy of the table not dropped quickly enough, a name conflict could occur on a subsequent ALTER TABLE. The scenario of commit `3792693f31` is unaffected by this fix, because mysqldump would use non-locking reads, and the transaction would not be holding any InnoDB locks during the execution of ROLLBACK TO SAVEPOINT. MVCC reads inside InnoDB are only covered by MDL and page latches, not by any table or record locks. FIXME: It would be nice if storage engines were specifically asked which MDL can be released, instead of only offering a choice between all or nothing. InnoDB should be able to release any locks for tables that are no longer in trx_t::mod_tables, except if another transaction had converted some implicit record locks to explicit ones, before the ROLLBACK TO SAVEPOINT had been completed. Reviewed by: Sergei Golubchik	4 years ago
Marko Mäkelä	5a2b625843	MDEV-25129 fixup: Adjust test result Fixup for commit `768c51880a`	4 years ago
Thirunarayanan Balathandayuthapani	e34877ab63	MDEV-25971 Instant ADD COLUMN fails to issue truncation warnings A table rebuild that would truncate the default value of a DATE column is expected to issue data truncation warnings. But, these warnings are not being issued if the ADD COLUMN is being executed with ALGORITHM=INSTANT. InnoDB sets the warning of the field while assigning the default value of the field during check_if_supported_inplace_alter().	4 years ago
Daniel Black	fa8eb4de55	mtr: plugin.multiauth aix fix The error loading the client module is different	4 years ago
Daniel Black	95e9f3c186	Merge branch 10.3 into 10.4	4 years ago
Daniel Black	6a3a046013	mtr: aix - no pool of threads	4 years ago
Daniel Black	2301093f8f	MDEV-25894: support AIX as a platform in mtr Parital backport of `48938c57c7` so platform dependent AIX tests can be done.	5 years ago
Daniel Black	7ce5984d6d	mtr: fix tests funcs_1.is_tables_is & sql_sequence.rebuild	4 years ago
Daniel Black	a88ddb168f	Merge branch '10.2' into 10.3	4 years ago
Daniel Black	c22f7f2323	MDEV-25129 postfix for windows C:\projects\server\sql\sql_show.cc(7913): error C2220: warning treated as error - no 'object' file generated [C:\projects\server\win_build\sql\sql.vcxproj] C:\projects\server\sql\sql_show.cc(7913): warning C4267: 'initializing': conversion from 'size_t' to 'uint', possible loss of data [C:\projects\server\win_build\sql\sql.vcxproj] caused by `768c51880a`	4 years ago
Daniel Black	0a9487b62b	mtr: aix - no pool of threads	4 years ago
Daniel Black	3f2c4758b0	MDEV-25894: support AIX as a platform in mtr Parital backport of `48938c57c7` so platform dependent AIX tests can be done.	5 years ago
Sergei Petrunia	c7443a0911	MDEV-25969: Condition pushdown into derived table doesn't work if select list uses SP Post-merge fix in 10.4: add a testcase for pushdown into IN subquery	4 years ago
Sergei Petrunia	eebe2090c8	Merge 10.3 -> 10.4	4 years ago
Sergei Petrunia	4a6e2d3437	Post-merge fix: update derived_cond_pushdown.result	4 years ago
Sergei Petrunia	586870f9ef	Merge 10.2->10.3	4 years ago
Sergei Petrunia	eb20c91b55	MDEV-25969: Condition pushdown into derived table doesn't work if select list uses SP Consider a query of the form: select ... from (select item2 as COL1) as T where COL1=123 Condition pushdown into derived table will try to push "COL1=123" condition down into table T. The process of pushdown involves "substituting" the item, that is, replacing Item_field("T.COL1") with its "producing item" item2. In order to use item2, one needs to clone it (call Item::build_clone). If the item is not cloneable (e.g. Item_func_sp is not), the pushdown process will fail and nothing at all will be pushed. Fixed by introducing transform_condition_or_part() which will try to apply the transformation for as many parts of condition as possible. The parts of condition that couldn't be transformed are dropped.	4 years ago
Jan Lindström	a1e2ca057d	MDEV-26030 : Warning: Memory not freed: 32 on setting wsrep_sst_auth Call to wsrep_sst_auth_free() was missing from normal shutdown.	4 years ago
xing-zhi, jiang	768c51880a	MDEV-25129 Add KEYWORDS view to the INFORMATION_SCHEMA Add KEYWORDS table and SQL_FUNCTIONS table to INFORMATION_SCHEMA. This commits needs some minor changes when propagated upwards (e.g. func_array in item_create.cc has a termination element that doesn't exist in later versions of MariaDB)	4 years ago
Marko Mäkelä	58252fff15	MDEV-26040 os_file_set_size() may not work on O_DIRECT files os_file_set_size(): Trim the current size down to the file system block size, to obey the constraints for unbuffered I/O.	4 years ago
Julius Goryavsky	6431862022	MDEV-25978 post-merge: updated mtr result files	4 years ago
Julius Goryavsky	58700a426a	MDEV-26019: Upgrading MariaDB breaks TLS mariabackup SST Fixed typo in variable name that breaks SST in some scenatios. Also fixed one small inaccuracy after MDEV-25978 which leads to the use of an uninitialized variable when the --log-bin option is specified without an argument.	4 years ago
Alexey Botchkov	8147d2e618	MDEV-25461 Assertion `je->state == JST_KEY' failed in Geometry::create_from_json. Handle invalid GEOJSON-s in Geometry::create_from_json().	4 years ago
Igor Babaev	4e4f742ed7	Adjusted test results after the fix for MDEV-20411 (2)	4 years ago
Igor Babaev	8b3f816cab	Adjusted test results after the fix for MDEV-20411	4 years ago

1 2 3 4 5 ...

190415 Commits (217caf27e3ac40fb83ee64ae9cf4012e908097d8) All Branches Search

190415 Commits (217caf27e3ac40fb83ee64ae9cf4012e908097d8)

All Branches