mariadb

Tree: 1ac0bce36e

Author	SHA1	Message	Date
Oleksandr Byelkin	1ac0bce36e	Merge branch '10.4' into 10.5	3 years ago
Oleksandr Byelkin	65e8506ca9	Merge branch '10.3' into bb-10.4-release	3 years ago
Nayuta Yanagisawa	faddcf3c39	Do not check symbol returned (or not and so there is some garbadge) by mb_wc() if mb_wc() failed	3 years ago
Sergei Golubchik	122742897b	my_safe_process: try to kill the process softly first first SIGTERM and if the process didn't die in 10 seconds, SIGKILL it. This allows various tools like `rr`, `gcov`, `gprof`, etc to flush their data to disk properly	3 years ago
Sergei Golubchik	9ecdf860ce	missing '	3 years ago
Sergei Golubchik	82c07fcabf	MDEV-23149 Server crashes in my_convert / ErrConvString::ptr / Item_char_typecast::check_truncation_with_warn	3 years ago
Sergei Golubchik	47d0df6ef0	take into account C/C specific CR_ERR_NET_WRITE error	3 years ago
Sergei Golubchik	9d4ed44cac	remove invalid options from warning messages --log-slow-queries was removed in 10.0. Now opt_slow_logname can be set either with --slow-query-log-file or with --log-basename --log was removed in 10.0. Now opt_logname can be set either with --general-log-file or with --log-basename	3 years ago
fluesvamp	50a2a8bb43	Update docs INSTALL BINARY to mention mariadb tar file instead	3 years ago
fluesvamp	f2830af16c	Fix typos in the codebase.	3 years ago
qggcs	195833f1b6	refactor: remove redundant assignments	3 years ago
Oleksandr Byelkin	c0fe31c5dd	fix of MDEV-12325 patch: symetric changes in sql_yacc_ora	3 years ago
Monty	4a53253cf9	Fixed that sp-no-valgrind.test is disabled on valgrind builds (not runs)	3 years ago
Monty	a5a9fcdfe4	MDEV-12325 Unexpected data type and truncation when using CTE When creating a recursive CTE, the column types are taken from the non recursive part of the CTE (this is according to the SQL standard). This patch adds code to abort the CTE if the calculated values in the recursive part does not fit in the fields in the created temporary table. The new code only affects recursive CTE, so it should not cause any notable problems for old applications. Other things: - Fixed that we get correct row numbers for warnings generated with WITH RECURSIVE Reviewer: Alexander Barkov <bar@mariadb.com>	3 years ago
Sergei Petrunia	3b071bad19	MDEV-29242: Assertion `computed_weight == weight' failed SEL_ARG::verify_weight Make SEL_ARG::make_root() maintain SEL_ARG::weight. Also, an unrelated change: fix dbug_print_sel_arg() to correctly print SQL NULL for the right endpoint.	3 years ago
Oleksandr Byelkin	ea12dafe65	Merge branch '10.4' into 10.5	3 years ago
Oleksandr Byelkin	6adfce9c8d	Merge branch '10.3' into 10.4	3 years ago
Daniel Black	43c7f6a0f3	MDEV-18702: mysqldump: add variable 'max-statement-time' (mtr fix) Disable for embedded as mysqldump cannot connect to embedded server.	3 years ago
Oleksandr Byelkin	b4c572f48a	Merge branch '10.3' into 10.4	3 years ago
Oleksandr Byelkin	992b510b2f	Fix compile errors.	3 years ago
Oleksandr Byelkin	c6406643cd	Fix compile errors.	3 years ago
Oleksandr Byelkin	1e71ea806b	Merge branch '10.4' into 10.5	3 years ago
Oleksandr Byelkin	e509065247	Merge branch '10.3' into 10.4	3 years ago
Sergei Petrunia	37a3d4467e	MDEV-23809: Server crash in JOIN_CACHE::free ...: part #2 Part #2: make sure we allocate space for two JOIN_TABs that use temporary tables. The dbug_join_tab_array_size is still set to catch cases where we try to access more JOIN_TAB object than we thought we would have.	3 years ago
Sergei Petrunia	2cd98c95de	MDEV-23809: Server crash in JOIN_CACHE::free or ... The problem was caused by use of COLLATION(AVG('x')). This is an item whose value is a constant. Name Resolution code called convert_const_to_int() which removed AVG('x'). However, the item representing COLLATION(...) still had with_sum_func=1. This inconsistent state confused the code that handles grouping and DISTINCT: JOIN::get_best_combination() decided to use one temporary table and allocated one JOIN_TAB for it, but then JOIN::make_aggr_tables_info() attempted to use two and made writes beyond the end of the JOIN::join_tab array. The fix: - Do not replace constant expressions which contain aggregate functions. - Add JOIN::dbug_join_tab_array_size to catch attempts to use more JOIN_TAB objects than we've allocated.	3 years ago
Thirunarayanan Balathandayuthapani	f9ec9b6abb	MDEV-27282 InnoDB: Failing assertion: !query->intersection - query->intersection fails to get freed if the query exceeds innodb_ft_result_cache_limit - errors from init_ftfuncs were not propogated by delete command This is taken from percona/percona-server@ef2c0bcb9a34aeb06de0058d7c2a2969416b35a7	3 years ago
Sergei Golubchik	cd51854d7a	RHEL9 disables SHA1 signatures in openssl with its 0049-Selectively-disallow-SHA1-signatures.patch in the openssl source rpm. let's allow them for now, this fixes tls_version and tls_version1 tests.	3 years ago
Sergei Golubchik	d7649968d9	MDEV-29220 Missing RHEL-9-specific logic in cpack_rpm.cmake	3 years ago
Oleksandr Byelkin	8fd8a81a99	Fix Oracle parser.	3 years ago
Oleksandr Byelkin	af143474d8	Merge branch '10.4' into 10.5	3 years ago
Igor Babaev	c2300d06f7	MDEV-28617 Crash with INSERT...SELECT using derived table in GROUP BY clause This bug manifested itself for INSERT...SELECT and DELETE statements whose WHERE condition used an IN/ANY/ALL predicand or a EXISTS predicate with such grouping subquery that: - its GROUP BY clause could be eliminated, - the GROUP clause contained a subquery over a mergeable derived table referencing the updated table. The bug ultimately caused a server crash when the prepare phase of the statement processing was executed. This happened after removal redundant subqueries used in the eliminated GROUP BY clause from the statement tree. The function that excluded the subqueries from the did not do it properly. As a result the specification of any derived table contained in a removed subquery was not marked as excluded. Approved by Oleksandr Byelkin <sanja@mariadb.com>	3 years ago
Sergei Golubchik	07a670b884	MDEV-23097 heap-use-after-free in mysqlimport mysqlimport starts many worker threads. when one of the worker encounters an error, it frees global memory and calls exit(). it suppresses memory leak detector, because, as the comment says "dirty exit, some threads are still running", indeed, it cannot free the memory from other threads. but precisely because some threads are still running, they might use this global memory, so it cannot be freed. fix: if we know that some threads are still running and accept that we cannot free all memory anyway, let's not free global allocations either	3 years ago
Daniel Black	92b0a367aa	MDEV-26447: mysqldump to use temporary view instead of tables. This is particularly important for Azure where there is no MyISAM support in their MariaDB cloud product. Like mysqldumper does, a view can satisfy the requirement like a table, without constraints. The views in frm files are text form and don't have column limits. Thanks Thomas Casteleyn for the suggestion.	3 years ago
Sergei Golubchik	7b500f04fb	MDEV-29078 For old binary logs explicit_defaults_for_timestamp presumed to be OFF, server value ignored don't assume anymore that OPTIONS_WRITTEN_TO_BIN_LOG is fixed once and forever. Instead, deduct master's OPTIONS_WRITTEN_TO_BIN_LOG from the master's version in binlog.	3 years ago
Sergei Golubchik	56c7d14217	MDEV-29075 Changing explicit_defaults_for_timestamp within stored procedure works inconsistently	3 years ago
Sergei Golubchik	b174ec169d	MDEV-29225 make explicit_defaults_for_timestamps SESSION variable save it in binlog, so that CREATE TABLE could be replayed correctly on the slave	3 years ago
Sergei Golubchik	4e3728f038	MDEV-29225 make explicit_defaults_for_timestamps SESSION variable make @@explicit_defaults_for_timestamp session variable	3 years ago
Sergei Golubchik	086eb8e23c	my_getopt --help for "bit" options print "Defaults to on" not only for GET_BOOL, but also for GET_BIT	3 years ago
Sergei Golubchik	28d44abd99	MDEV-27540 Different OpenSSL versions mix up in build depending on cmake options list ${OPENSSL_ROOT_DIR}/lib64 explicitly, because cmake below version 3.23.0 won't search there.	4 years ago
Oleksandr Byelkin	48e35b8cf6	Merge branch '10.3' into 10.4	3 years ago
Mike Griffin	53c4e4d054	MDEV-18702 mysqldump: add variable 'max-statement-time' With a global non-default max-statement-time of a time interval that exceed the query time mysqldump queries when doing a backup. To solve both, add a max-statement-time option, defaulting to 0 (unlimited time). Also like mariabackup, set the session wait_timeout=DEFAULT (28800). The time/processing between mysqldump times isn't expected to get that close ever, but let's adopt the standard of mariabackup as no-one has challenged it has having a detrimental effect. Reviewer and test case author Daniel Black	3 years ago
Oleksandr Byelkin	5ac528a91f	Merge remote-tracking branch 'connect/10.3' into 10.3	3 years ago
Oleksandr Byelkin	b043e1098e	Merge branch 'merge-perfschema-5.7' into 10.5	3 years ago
Ian Gilfillan	4d0c53a327	MDEV-28701 Update Server HELP Bootstrap size increase and error fix by Daniel Black.	3 years ago
Daniel Black	182a6383cd	MDEV-16605 Always include buf_madvise_do_dump in binaries The "used" attribute seems to do this ref: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#Common-Function-Attributes	3 years ago
Aleksey Midenkov	1ea5e402a8	MDEV-28727 ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade MDEV-20704 changed the rules of how (HA_BINARY_PACK_KEY \| HA_VAR_LENGTH_KEY) flags are added. Older FRMs before that fix had these flags for DOUBLE index. After that fix when ALTER sees such old FRM it thinks it cannot do instant alter because of failed compare_keys_but_name(): it compares flags against tmp table created by ALTER. MDEV-20704 fix was actually not about DOUBLE type but about FIELDFLAG_BLOB which affected DOUBLE. So there is no direct knowledge that any other types were not affected. The proposed fix under CHECK TABLE checks if FRM has (HA_BINARY_PACK_KEY \| HA_VAR_LENGTH_KEY) flags and was created prior MDEV-20704 and if so issues "needs upgrade". When mysqlcheck and mysql_upgrade see such status they issue ALTER TABLE FORCE and upgrade the table to the version of server.	3 years ago
Aleksey Midenkov	231feabd2b	MDEV-21540 Initialization of already inited long unique index on reorganize partition Handler for existing partition was already index-inited at the beginning of copy_partitions(). In the case of REORGANIZE PARTITION we fill new partition by calling its ha_write_row() (handler is storage engine of new partition). From that we go through the below conditions: if (this->inited == RND) table->clone_handler_for_update(); handler *h= table->update_handler ? table->update_handler : table->file; First, the above misses the meaning of this->inited check. Now it is new partition and this handler is not inited. So, we assign table->file which is ha_partition and is really not known to be inited or not. It is supposed (this == table->file), otherwise we are out of the logic for using update_handler. This patch adds DBUG_ASSERT for that. Second, we call check_duplicate_long_entries() for table->file and that calls ha_partition::index_init() which calls index_init() for each partition's handler. But the existing parititions' handlers was already inited in copy_partitions() and we fail on assertion. The fix implies that we don't need check_duplicate_long_entries() per-partition as we've already done check_duplicate_long_entries() for ha_partition. For REORGANIZE PARTITION that means existing row was already checked at previous INSERT/UPDATE commands, so no need to check it again (see NOTE in handler::ha_write_row()). The fix also optimizes ha_update_row() so check_duplicate_long_entries_update() is not called per-partition considering it was already called for ha_partition. Besides, per-partition duplicate check is not really usable.	3 years ago
Julius Goryavsky	7fb1f919d0	MDEV-28758: Mariabackup copies binary logs to backup directory This commit restores defaults and functionality regarding binlogs to the way it was prior to MDEV-27524. The mariabackup utility no longer saves binlogs files as part of a backup without the --galera-info option. However, since we use --galera-info during SST, the behavior of mariabackup changes and, in combination with GTIDs support enabled, mariabackup transfers one (most recent) binlog file obtained after FLUSH BINARY LOGS. In other cases, binlogs are not transferred during SST in mariabackup mode. As for SST in the rsync mode, it works the same way as before MDEV-27524 - by default it transfers one last binlog file. The --sst-max-binlogs option for mariabackup and the sst_max_binlogs parameter in the [sst] / server sections are no longer supported for SST via mariabackup.	3 years ago
Sergei Golubchik	5b4154373a	only copy buffer pool dump in SST galera mode and then only into the default name, so that the joiner could find it	3 years ago
Sergei Golubchik	5197519f4f	revert mariabackup part of MDEV-27524, fix the test	3 years ago

1 2 3 4 5 ...

194247 Commits (1ac0bce36e5bf2136cedb1ce1da949f53cce4404) All Branches Search

194247 Commits (1ac0bce36e5bf2136cedb1ce1da949f53cce4404)

All Branches