mariadb

Tree: 70c11485d2

Author	SHA1	Message	Date
Marko Mäkelä	70c11485d2	Remove MYSQL_ENCRYPTION. MariaDB will likely never support MySQL-style encryption for InnoDB, because we cannot link with the Oracle encryption plugin. This is preparation for merging MDEV-11623.	9 years ago
Sergei Petrunia	45f11a729c	MDEV-10773: ANALYZE FORMAT=JSON query_with_CTE crashes Added testcase	9 years ago
Marko Mäkelä	6a65de6cda	Correct a test broken in the merge `7c81f15ec3`	9 years ago
Marko Mäkelä	c849b7df61	MDEV-11785 Remove INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO The INFORMATION_SCHEMA view INNODB_TEMP_TABLE_INFO was added to MySQL 5.7 as part of the work to implement temporary tables without any redo logging. The only use case of this view was SELECT COUNT(*) in some tests, to see how many temporary tables exist in InnoDB. The columns do not report much useful information. For example, the table name would not be the user-specified table name, but a generated #sql name. Also, the session that created the table is not identified.	9 years ago
Marko Mäkelä	bb109aeea3	MDEV-6076: Fix a broken assertion.	9 years ago
Marko Mäkelä	1ba7234b21	Follow-up to MDEV-11713: Make more use of DBUG_LOG	9 years ago
Marko Mäkelä	7c81f15ec3	Merge 10.1 into bb-10.2-mdev-11782	9 years ago
Marko Mäkelä	2dc5d8bb7e	Improve an MDEV-9011 test of innodb_encrypt_log. Test crash recovery from an encrypted redo log with innodb_encrypt_log=0. Previously, we did a clean shutdown, so only the log checkpoint information would have been read from the redo log. With this change, we will be reading and applying encrypted redo log records. include/start_mysqld.inc: Observe $restart_parameters. encryption.innodb-log-encrypt: Remove some unnecessary statements, and instead of restarting the server and concurrently accessing the files while the server is running, kill the server, check the files, and finally start up the server. innodb.log_data_file_size: Use start_mysqld.inc with $restart_parameters.	9 years ago
Marko Mäkelä	fd0479ce59	Merge 10.1 into 10.2	9 years ago
Marko Mäkelä	4507f1e5d4	Remove an excessive copyright message.	9 years ago
Marko Mäkelä	5b5bce81e6	Merge 10.0 into 10.1	9 years ago
Marko Mäkelä	833fda8f1a	InnoDB: Enable UNIV_DEBUG_VALGRIND for cmake -DWITH_VALGRIND The symbol HAVE_VALGRIND_MEMCHECK_H was never defined. Instead, the symbol HAVE_VALGRIND should have been used.	9 years ago
Monty	5f0c31f928	MDEV-11597 Assertion when doing select from virtual column with impossible value - Changed error handlers interface so that they can change error level in the handler - Give warnings and errors when calculating virtual columns - On insert/update error is fatal in strict mode. - SELECT and DELETE will only give a warning if a virtual field generates an error - Added VCOL_UPDATE_FOR_DELETE and VCOL_UPDATE_INDEX_FOR_REPLACE to be able to easily detect in update_virtual_fields() if we should use an error handler to mask errors or not.	9 years ago
Monty	177c191ff4	MDEV-11606 Server crashes in mi_make_key / sort_key_read Problem was that one internal record buffer in MYISAM was not big enough to handle virtual fields. Fixed by extending buffer. Fixed test case to 79 characters	9 years ago
Monty	c9b3e4535b	MDEV-11737 Failing assertion: block->magic_n == MEM_BLOCK_MAGIC_N Issue was that the m_prebuilt array was reused without resetting a counter, which caused a memory overrun. Adjusted test case to 79 characters	9 years ago
Monty	6c5c98316f	Updated mysql-test/README with information about KB	9 years ago
Monty	135e144479	MDEV-11598 Assertion `!table \|\| (!table->read_set \|\| bitmap_is_set(table->read_set, field_index))' failed Found and fixed 2 problems: - Filesort addon fields didn't mark virtual columns properly - multi-range-read calculated vcol bitmap but was not using it. This caused wrong vcol field to be calculated on read, which caused the assert.	9 years ago
Monty	de22cd3fe5	Fixes for failures in test scripts and removal of some compiler warnings - rpl_gtid_stop_start: Random failure - sysvars_innodb,32bit: Fixes for 32 bit	9 years ago
Monty	bf95970ec0	Cleanups * Ensure that BUILD scripts cleans up things properly before new BUILD * MySQL -> MariaDB * Ignore wrong valgrind memleak	9 years ago
Sergei Golubchik	53ae72e2ee	mtr uses dgcov for --gcov option	9 years ago
Sergei Golubchik	00f462cf1b	dgcov: import, rewrite to work with cmake and git	9 years ago
Monty	7567cf5aef	Fixes for using ssl with BUILD scripts. Needed as GNUTLS can't be used by MariaDB on many systems, like OpenSuse 13.2	9 years ago
Monty	ea1b25046c	New simpler bugfix for UPDATE and virtual BLOBs When updating a table with virtual BLOB columns, the following might happen: - an old record is read from the table, it has no virtual blob values - update_virtual_fields() is run, vcol blob gets its value into the record. But only a pointer to the value is in the table->record[0], the value is in Field_blob::value String (but it doesn't have to be! it can be in the record, if the column is just a copy of another columns: ... b VARCHAR, c BLOB AS (b) ...) - store_record(table,record[1]), old record now is in record[1] - fill_record() prepares new values in record[0], vcol blob is updated, new value replaces the old one in the Field_blob::value - now both record[1] and record[0] have a pointer that points to the new vcol blob value. Or record[1] has a pointer to nowhere if Field_blob::value had to realloc. To fix this I have introduced a new String object 'read_value' in Field_blob. When updating virtual columns when a row has been read, the allocated value is stored in 'read_value' instead of 'value'. The allocated blobs for the new row is stored in 'value' as before. I also made, as a safety precaution, the insert delayed handling of blobs more general by using value to store strings instead of the record. This ensures that virtual functions on delayed insert should work in as in the case of normal insert. Triggers are now properly updating the read, write and vcol maps for used fields. This means that we don't need VCOL_UPDATE_FOR_READ_WRITE anymore and there is no need for any other special handling of triggers in update_virtual_fields(). To be able to test how many times virtual fields are invoked, I also relaxed rules that one can use local (@) variables in DEFAULT and non persistent virtual field expressions.	9 years ago
Monty	7454087d07	Revert "bugfix: UPDATE and virtual BLOBs" This reverts commit `f73bdb685d`.	9 years ago
Monty	1628a2ae27	Fixed issues found by buildbot - MDEV-11621 rpl.rpl_gtid_stop_start fails sporadically in buildbot - MDEV-11620 rpl.rpl_upgrade_master_info fails sporadically in buildbot The issue above was probably that the build machine was overworked and the shutdown took longer than 30 resp 10 seconds, which caused MyISAM tables to be marked as crashed. Fixed by flushing myisam tables before doing a forced shutdown/kill. I also increased timeout for forced shutdown from 10 seconds to 60 seconds to fix other possible issues on slow machines. Fixed also some compiler warnings	9 years ago
Monty	1afb17047a	Fixed bugs found by mysql-test-run: - privilege_table_io.test didn't properly reset roles_mapping - Fixed memory allocation problem with CHECK CONSTRAINT, found when running --valgrind main.check_constraint	9 years ago
Sergei Golubchik	ed008a74cf	Make atomic writes general - Atomic writes are enabled by default - Automatically detect if device supports atomic write and use it if atomic writes are enabled - Remove ATOMIC WRITE options from CREATE TABLE - Atomic write is a device option, not a table options as the table may crash if the media changes - Add support for SHANNON SSD cards	9 years ago
Monty	ed0bc17bee	Removed usage of my_hash_search() with uninitialized HASH. - Not documented on intened usage - Extra checking takes time for all HASH usage	9 years ago
Monty	e80ad58de8	Improve mysys/hash by caching hash_nr This is done without using any additional memory Added internal test case This is similar to MDEV-7716	9 years ago
Monty	67034b6d52	Fixes for running with gcov	9 years ago
Elena Stepanova	f516db3500	Updated list of unstable tests for 10.0.29 release	9 years ago
Marko Mäkelä	f27ca6f667	Merge 10.1 into 10.2	9 years ago
Marko Mäkelä	5044dae239	Merge 10.0 into 10.1	9 years ago
Marko Mäkelä	78e6fafcaa	Fix an innodb_plugin leak noted in MDEV-11686 buf_flush_init_flush_rbt() was called too early in MariaDB server 10.0, 10.1, MySQL 5.5 and MySQL 5.6. The memory leak has been fixed in the XtraDB storage engine and in MySQL 5.7. As a result, when the server is started to initialize new data files, the buf_pool->flush_rbt will be created unnecessarily and then leaked. This memory leak was noticed in MariaDB server 10.1 when running the test encryption.innodb_first_page.	9 years ago
Alexey Botchkov	171e59ed47	MDEV-11548 Reproducible server crash after the 2nd ALTER TABLE ADD FOREIGN KEY IF NOT EXISTS. Have to use 'keyname' to check the name uniqueness.	9 years ago
Marko Mäkelä	3d46768da2	Merge 10.1 into 10.2	9 years ago
Marko Mäkelä	4b05d60e62	Make encryption.innodb_lotoftables more robust. Perform a slow shutdown at the start of the test, and create all InnoDB tables with STATS_PERSISTENT=0, so that any I/O related to background tasks (change buffer merge, purge, persistent statistics) should be eliminated.	9 years ago
Marko Mäkelä	59ea6456c3	Minor cleanup of innodb.innodb-change-buffer-recovery This should be a non-functional change. I was unable to repeat MDEV-11626 innodb.innodb-change-buffer-recovery fails for xtradb and cannot determine the reason for the failure without having access to the files. The repeatability of MDEV-11626 should not be affected by these changes.	9 years ago
Monty	eed319b6fb	MDEV-11317: `! is_set()' or `!is_set() \|\| (m_status == DA_OK_BULK && is_bulk_op())' fails in Diagnostics_area::set_ok_status on CREATE OR REPLACE with ARCHIVE table Problem was with deleting non existing .frm file for a storage engine that doesn't have .frm files (yet) Fixed by not giving an error for non existing .frm files for storage engines that are using discovery Fixed also valgrind supression related to the given test case	9 years ago
Marko Mäkelä	8773a5e161	Post-fix MDEV-11695 Define a reasonable upper limit for innodb_spin_wait_delay Change the parameter type from ulong to uint, so that 32-bit and 64-bit systems will report an identical result.	9 years ago
Marko Mäkelä	6790bf049c	Merge 10.1 into 10.2	9 years ago
Marko Mäkelä	384f4d1e36	Post-push fix for MDEV-11556: Make the debug variable UINT. Sometimes innodb_data_file_size_debug was reported as INT UNSIGNED instead of BIGINT UNSIGNED. Make it uint instead of ulong to get a more deterministic result.	9 years ago
Vladislav Vaintroub	eaf6b053b8	MDEV-11087 Search path for my.ini is wrong for default installation Add <install_root>/data/my.ini to the search path - this my.ini location is used since MariaDB 5.2	9 years ago
Vladislav Vaintroub	82b8741ad0	Windows : use meaningful DEFAULT_MYSQL_HOME - base directory for the default installation. It is now defined as "C:/Program Files/MariaDB ${MYSQL_BASE_VERSION}" which is where installer indeed puts it by default. It still does not cover every case -32bit installer on 64 bit Windows would put installation root under "C:/Program Files (x86)", but better than the path used previously C:/MariaDB${MYSQL_BASE_VERSION}, which was never correct.	9 years ago
Vladislav Vaintroub	ae6eb7a002	MDEV-11088 Client plugins cannot be loaded by command line tools in default installation. Added plugin-dir to the [client] section of the generated my.ini, so that installed services (MSI or mysql_install_db.exe) would be able to find plugin directory.	9 years ago
Marko Mäkelä	bbd4844a43	Suppress warnings of NUMA not working.	9 years ago
Marko Mäkelä	ac0b0efa14	Post-fix MDEV-11695 Define a reasonable upper limit for innodb_spin_wait_delay Adjust the tests.	9 years ago
Dmitry Lenev	e4978d26b7	MDEV-9084 Calling a stored function from a nested select from temporary table causes unpredictable behavior Cherry-pick: `f4a0af070c` Author: Dmitry Lenev <dmitry.lenev@oracle.com> Date: Mon Jul 25 16:06:52 2016 +0300 Fix for bug #16672723 "CAN'T FIND TEMPORARY TABLE". Attempt to execute prepared CREATE TABLE SELECT statement which used temporary table in the subquery in FROM clause and stored function failed with unwarranted ER_NO_SUCH_TABLE error. The same happened when such statement was used in stored procedure and this procedure was re-executed. The problem occurred because execution of such prepared statement/its re-execution as part of stored procedure incorrectly set Query_table_list::query_tables_own_last marker, indicating the last table which is directly used by statement. As result temporary table used in the subquery was treated as indirectly used/belonging to prelocking list and was not pre-opened by open_temporary_tables() call before statement execution. Thus causing ER_NO_SUCH_TABLE errors since our code assumes that temporary tables need to be correctly pre-opened before statement execution. This problem became visible only in version 5.6 after patches related to bug 11746602/27480 "EXTEND CREATE TEMPORARY TABLES PRIVILEGE TO ALLOW TEMP TABLE OPERATIONS" since they have introduced pre-opening of temporary tables for statements. Incorrect setting of Query_table_list::query_tables_own_last happened in LEX::first_lists_tables_same() method which is called by CREATE TABLE SELECT implementation as part of LEX::unlink_first_table(), which temporary excludes table list element for table being created from the query table list before handling SELECT part. LEX::first_lists_tables_same() tries to ensure that global table list of the statement starts with the first table list element from the first statement select. To do this it moves such table list element to the head of the global table list. If this table happens to be last directly-used table for the statement, query_tables_own_last marker is pointing to it. Since this marker was not updated when table list element was moved we ended up with all tables except the first table separated by it as if they were not directly used by statement (i.e. belonged to prelocked tables list). This fix changes code of LEX::first_lists_tables_same() to update query_tables_own_last marker in cases when it points to the table being moved. It is set to the table which precedes table being moved in this case.	9 years ago
Kristian Nielsen	43378f367c	MDEV-10271: Stopped SQL slave thread doesn't print a message to error log like IO thread does Make the slave SQL thread always output to the error log the message "Slave SQL thread exiting, replication stopped in ..." whenever it previously outputted "Slave SQL thread initialized, starting replication ...". Before this patch, it was somewhat inconsistent in which cases the message would be output and in which not, depending on the exact time and cause of the condition that caused the SQL thread to stop.	9 years ago
Elena Stepanova	670b85804c	Replication tests fail on valgrind due to waiting-related timeouts MTR raises default wait_for_pos_timeout from 300 to 1500 when tests are run with valgrind. The same needs to be done for other replication-related waits. The change should fix one of failures mentioned in MDEV-10653 (rpl.rpl_parallel fails in buildbot with timeout), the one on the valgrind builder; but not all of them	9 years ago

1 2 3 4 5 ...

176025 Commits (70c11485d2d5982ffbf31740b24798565760a16f) All Branches Search

176025 Commits (70c11485d2d5982ffbf31740b24798565760a16f)

All Branches