mariadb

Tree: 24503d5711

Author	SHA1	Message	Date
Rasmus Johansson	24503d5711	MDEV-17592 Create MariaDB named commands/symlinks	7 years ago
Sergei Golubchik	f02bc3cf0f	change pam and disks plugin maturity beta->gamma	6 years ago
Sergei Golubchik	da619f010f	compilation fix for fulltest-big	6 years ago
Sergei Golubchik	20bb4ed15e	make the heap.heap test portable in HEAP btree indexes, the address of a record in memory is part of the key. So, when inserting many identical keys, the actual btree shape is defined by how and where records in memory are allocated. records_in_range uses floats to estimate the size of the chunk of the btree between min and max records, it depends on the btree shape and, thus, is not portable either. As are optimizer decisions that are based on records_in_range estimations, if the number happens to be close to a tipping point. as a fix, reduce the number of matching rows, so that even with system-specific variations the optimizer would still pick the expected plan. Fixes heap.heap failure (range vs ALL) on ppc64	6 years ago
Sergei Golubchik	13e8f728ec	compilation failure on ppc with -DCMAKE_BUILD_TYPE=Debug if ${CRC32_LIBRARY} target has no COMPILE_FLAGS yet, GET_TARGET_PROPERTY returns COMPILE_FLAGS-NOTFOUND, which doesn't work very well when it's later fed back into COMPILE_FLAGS. GET_PROPERTY() returns an empty string in this case.	6 years ago
Sergei Golubchik	0933212036	C/C	6 years ago
Sergei Golubchik	a4cc6fb91f	MDEV-15526 SysV init service deployed file '/etc/init.d/mysql' prevents systemctl disable command to work correctly (mariadb\|mysql naming support) (debian/ubuntu) mariadb service is controlled by systemd Do not install SysV init script on Debian/Ubuntu in /etc/init.d/ put it in /usr/share/mysql in case the user would need it for something. Use systemctl in pre/post scripts directly without funky conditionals and wrapper scripts	6 years ago
Sergei Golubchik	0a43df4fbc	MDEV-14735 better matching order for grants fixes MDEV-14732 mysql.db privileges evaluated on order of grants rather than hierarchically MDEV-8269 Correct fix for Bug #20181776 :- ACCESS CONTROL DOESN'T MATCH MOST SPECIFIC HOST WHEN IT CONTAINS WILDCARD reimplement the old ad hoc get_sort() function to use a wildcard pattern ordering logic that works correctly in may be all practical cases. get_sort() is renamed to catch merge errors at compilation time. moved to a separate included file, because of a long comment.	6 years ago
Sergei Golubchik	fd00c449e3	bugfix: PROXY privilege matched usernames incorrectly username can be empty, meaning anybody, or must match literally. only db and host names are matched with wildcards.	6 years ago
Georg Richter	d13080133f	MDEV-14101 Provide an option to select TLS protocol version Server and command line tools now support option --tls_version to specify the TLS version between client and server. Valid values are TLSv1.0, TLSv1.1, TLSv1.2, TLSv1.3 or a combination of them. E.g. --tls_version=TLSv1.3 --tls_version=TLSv1.2,TLSv1.3 In case there is a gap between versions, the lowest version will be used: --tls_version=TLSv1.1,TLSv1.3 -> Only TLSv1.1 will be available. If the used TLS library doesn't support the specified TLS version, it will use the default configuration. Limitations: SSLv3 is not supported. The default configuration doesn't support TLSv1.0 anymore. TLSv1.3 protocol currently is only supported by OpenSSL 1.1.0 (client and server) and GnuTLS 3.6.5 (client only). Overview of TLS implementations and protocols Server: +-----------+-----------------------------------------+ \| Library \| Supported TLS versions \| +-----------+-----------------------------------------+ \| WolfSSL \| TLSv1.1, TLSv1,2 \| +-----------+-----------------------------------------+ \| OpenSSL \| (TLSv1.0), TLSv1.1, TLSv1,2, TLSv1.3 \| +-----------+-----------------------------------------+ \| LibreSSL \| (TLSv1.0), TLSv1.1, TLSv1,2, TLSv1.3 \| +-----------+-----------------------------------------+ Client (MariaDB Connector/C) +-----------+-----------------------------------------+ \| Library \| Supported TLS versions \| +-----------+-----------------------------------------+ \| GnuTLS \| (TLSv1.0), TLSv1.1, TLSv1.2, TLSv1.3 \| +-----------+-----------------------------------------+ \| Schannel \| (TLSv1.0), TLSv1.1, TLSv1.2 \| +-----------+-----------------------------------------+ \| OpenSSL \| (TLSv1.0), TLSv1.1, TLSv1,2, TLSv1.3 \| +-----------+-----------------------------------------+ \| LibreSSL \| (TLSv1.0), TLSv1.1, TLSv1,2, TLSv1.3 \| +-----------+-----------------------------------------+	6 years ago
Sergei Golubchik	379ffc6eaa	MDEV-19765 Bug in CMakeLists.txt introduced by MDEV-11670 fix a typo followup for `6e5c246639`	6 years ago
Sergei Golubchik	b3f3b3eaca	fix versioning.simple for embedded	6 years ago
Sergei Golubchik	7ad1e4a546	fix tests, failing after `daf333abcf`	6 years ago
Michael Widenius	daf333abcf	Rename of stat table tried to rename open table. When compiling with -DEXTRA_DEBUG and run main.stat_tables_missing on go the warning: Warning: Table: ./mysql/column_stats is open on rename old_table This happened because rename_table_in_stat_tables() re-open the table that was to be renamed. Fixed by moving update of stat tables after all renames has been made.	6 years ago
Oleksandr Byelkin	bff7cf9df8	Fix of fail of period.updtae with ps protocol.	6 years ago
Vladislav Vaintroub	bf90a486c3	Do not use LEX_CSTRING in printf-like function	6 years ago
Oleksandr Byelkin	f66d1850ac	Merge branch '10.3' into 10.4	6 years ago
Varun	772c5f3c78	MDEV-19634: Assertion `0' failed in row_sel_convert_mysql_key_to_innobase, [Warning] InnoDB: Using a partial-field key prefix in search For a key with keyparts (k1,k2,k3) , if we are building a range over the keyparts we should make sure that if min_value/max_value for a keypart is not added to key buffer then the keyparts following should also not be allowed.	6 years ago
Vladislav Vaintroub	1e3dc15d62	Use generated user_settings.h for WolfSSL, as recommended by WolfSSL documentation Apparently, WolfSSL wants to have exactly the same defines for the user of the library as the was when building library itself. A lot of #defines have an impact on ABI (structure sizes, alignment etc)	7 years ago
Vladislav Vaintroub	4ec302ebf8	WolfSSL : Fix crosscompiling i386 on x86_64, on Linux	6 years ago
faust	e22d2cfe58	fix typo support-files/mariadb@.service.in Co-Authored-By: grooverdan <daniel@linux.ibm.com>	7 years ago
Daniel Black	764a10a926	MDEV-11670: mariadb@.service remove alias, clean up documentation/order	7 years ago
Daniel Black	6e5c246639	MDEV-11670: ensure sysconfdir/sysconf2dir are not blank for mariadb@.service	7 years ago
Daniel Black	91f1694836	systemd: multi-instance not for Galera, User/Group flexible By removing Galera functionality, we remove PermissionsStartOnly=true and hence make this service more flexible for running multiple instances each on a different user.	7 years ago
Daniel Black	3a0a570e0b	systemd: multi-instance changes to -defaults-group-suffix=.%I When the multi-instance systemd service file was chosen it effectively relied on /etc/my.cnf.d/my{instancename}.cnf file to define its configuration file. This is problematic if running along side a single instance mariadb service which has /etc/my.cnf that reads all configuration file /etc/my.cnf.d/*.cnf. To prevent the service from auto starting up if a user has this previous configuration ConditionPathExists=!@sysconf2dir@/my%I.cnf to ensure that a user with the previous configuration isn't started in a non-intended mode. Documentation in the service file (should be release notes too), described a recommended migration. A new approach was to use --defaults-group-suffix=.%I as an arguement to mysqld and let the user define a [mysqld.{instancename}] group within the configuration file. This way existing global mysqld configuration options are read with the instance name having special overrides of datadir, port, socket etc. A systemd environment variable MYSQLD_MULTI_INSTANCE is used in the defination as it give the user flexability to use multiple segregation mechanisms between services. This is used multiple times within the service which all needed to be kept consistent. Another notable change is mysql_install_db being part of the ExecStartPre. This provides and auto-initialization for users that run multiple instances.	8 years ago
Oleksandr Byelkin	1135244a64	Merge branch '10.2-release' into 10.3-release	6 years ago
Sergei Golubchik	b40c2d2c51	MDEV-19633 ASAN use-after-poison in tree_insert() in main.func_gconcat when copying the TREE, take into account that init_tree can internally adjust tree->size_of_element	6 years ago
Aleksey Midenkov	2e73561c6c	MDEV-16804 SYSTEM VERSIONING columns not showing as GENERATED Closes #830	7 years ago
Oleksandr Byelkin	4a3d51c76c	Merge branch '10.2' into 10.3	6 years ago
Marko Mäkelä	e5fab61a73	MDEV-6275: Use a non-narrowing conversion On 32-bit systems, sizeof(uint)==sizeof(long). The C++11 narrowing cast would issue a warning due to the sign mismatch.	6 years ago
Marko Mäkelä	2cd45add27	MDEV-6275: Fix signed/unsigned comparison	6 years ago
Marko Mäkelä	991d5140c3	Merge 10.3 into 10.4	6 years ago
Marko Mäkelä	d9fe615ef6	spider_db_init(): Do not return uninitialized error_num If the allocation of spider_table_sts_threads failed, we would DBUG_RETURN(error_num) without having initialized it earlier. Pre-initialize error_num to HA_ERR_OUT_OF_MEM and remove a lot of assignments that thus became redundant. This error was introduced in `207594afac` (Spider 3.3.13).	6 years ago
Oleksandr Byelkin	50653e021f	Merge branch '10.1' into 10.2	6 years ago
Thirunarayanan Balathandayuthapani	e9145aab44	MDEV-19435 buf_fix_count > 0 for corrupted page when it exits the LRU list Problem: ========= One of the purge thread access the corrupted page and tries to remove from LRU list. In the mean time, other purge threads are waiting for same page in buf_wait_for_read(). Assertion(buf_fix_count == 0) fails for the purge thread which tries to remove the page from LRU list. Solution: ======== - Set the page id as FIL_NULL to indicate the page is corrupted before removing the block from LRU list. Acquire hash lock for the particular page id and wait for the other threads to release buf_fix_count for the block. - Added the error check for btr_cur_open() in row_search_on_row_ref().	6 years ago
Jan Lindström	371a8a6615	Galera test cleanup.	6 years ago
Oleksandr Byelkin	5b65d61d93	Merge branch '5.5' into 10.1	6 years ago
Marko Mäkelä	06be8cd38f	Clean up the test innodb.innodb-64k-crash Before killing the server, ensure that the incomplete state of the transaction will be made durable and will be applied and rolled back on recovery, so that each time, roughly the same amount of work will be done. Remove DML statements after the recovery, and execute CHECK TABLE instead.	6 years ago
Marko Mäkelä	1d31bed212	Merge 10.1 into 10.2	6 years ago
Marko Mäkelä	56c60b2fc5	MDEV-16111 encryption.innodb_lotoftables failed in buildbot with wrong result Remove the test, because it easily fails with a result difference. Analysis by Thirunarayanan Balathandayuthapani: By default, innodb_encrypt_tables=0. 1) Test case creates 100 tables in innodb_encrypt_1. 2) creates another 100 unencrypted tables (encryption=off) in innodb_encrypt_2 3) creates another 100 encrypted tables (encryption=on) in innodb_encrypt_3 4) enabling innodb_encrypt_tables=1 and checking that only 100 encrypted tables exist. (already we have 100 in dictionary) 5) opening all tables again (no idea why) 6) After that, set innodb_encrypt_tables=0 and wait for 100 tables to be decrypted (already we have 100 unencrypted tables) 7) dropping all databases Sporadic failure happens because after step 4, it could encrypt the normal table too, because innodb_encryption_threads=4. This test was added in MDEV-9931, which was about InnoDB startup being slow due to all .ibd files being opened. There have been a number of later fixes to this problem. Currently the latest one is commit `cad56fbaba`, in which some tests (in particular the test innodb.alter_kill) could fail if all InnoDB .ibd files are read during startup. That could make this test redundant. Let us remove the test, because it is big, slow, unreliable, and does not seem to reliably catch the problem that all files are being read on InnoDB startup.	6 years ago
Marko Mäkelä	90fec9602f	Merge 10.1 into 10.2	6 years ago
Marko Mäkelä	94e665596d	MDEV-19740: Remove some broken InnoDB systemd code GCC 9.1.1 noticed that sd_notifyf() was always being invoked with str=NULL argument for "%s". This code was added in commit `2e814d4702` but not mentioned in the commit comment. The STATUS messages for systemd matter during startup and shutdown, and should not be emitted during normal operation. ib_senderrf(): Remove the potentially harmful sd_notifyf() calls.	6 years ago
Kentoku SHIBA	8e3a4be45c	MDEV-6275 spider_same_server_link not enforced (#1330 )	6 years ago
sjaakola	efc3cb9322	MDEV-19563 Removed references to deprecated option innodb_locks_unsafe_for_binlog innodb_locks_unsafe_for_binlog variabe removed from wsrep_info test configuration and recommendation to use this variable in README-wsrep was removed as well Also relates to issue: MDEV-19544	6 years ago
Sergey Vojtovich	9d886de499	MDEV-16467 - MariaDB crashes because of "long semaphore wait"after migrating from 10.1 to 10.3 This patch fixes 10.2 issue reported in MDEV-16467 by partial backport of `c2118a0`. Specifically "Remove not needed LOCK_thread_count from thd_get_error_context_description()".	6 years ago
Marko Mäkelä	4bbd8be482	Merge 10.1 into 10.2	6 years ago
Thirunarayanan Balathandayuthapani	b2f76bac03	MDEV-16866 InnoDB fails to start upon crash recovery with "[ERROR] InnoDB: Redo log crypto: failed to decrypt log block" - Post-push fix to change the copyright of both xtradb and innodb file.	6 years ago
Thirunarayanan Balathandayuthapani	c5fe1b8fc1	MDEV-16866 InnoDB fails to start upon crash recovery with "[ERROR] InnoDB: Redo log crypto: failed to decrypt log block" - If InnoDB encounters garbage or incomplete written log block during recovery then don't throw the error. Treat it as end of the log. - This kind of incomplete or empty block can be result of killing InnoDB when writing the redo log.	6 years ago
Marko Mäkelä	2fd82471ab	Merge 10.3 into 10.4	6 years ago
Jan Lindström	cf78b8c699	Merge 10.2 into 10.3	6 years ago

1 2 3 4 5 ...

186193 Commits (24503d5711677ce77617e3ff2514a4838e95eac7) All Branches Search

186193 Commits (24503d5711677ce77617e3ff2514a4838e95eac7)

All Branches