mariadb

Tree: 9ef2d29ff4

Author	SHA1	Message	Date
Sergei Golubchik	51a9571256	MDEV-20205 mysql_install_db shouldn't execute chown Make chown error non-fatal. Just print a warning.	6 years ago
Sergei Golubchik	9d18b62467	rpm/deb and auth_pam_tool_dir/auth_pam_tool don't let mysql_install_db set SUID bit for auth_pam_tool in rpm/deb packages - instead package files with correct permissions and only fix the ownership of auth_pam_tool_dir (which can only be done after mysql user is created, so in post-install). keep old mysql_install_db behavior for bintars	6 years ago
Sergei Golubchik	744d545fd7	restore support for --defaults-file=<(...) if my_realpath() fails, don't return the error code, get_defaults_options() returns a number of options consumed, not 0=ok/1=error. instead, ignore the error from my_realpath. If it fails it internally falls back to my_load_path, which restores 10.4- behavior	6 years ago
Sergei Golubchik	8bcbdaf730	cleanup: remove unused arguments	6 years ago
Marko Mäkelä	02af6278fb	InnoDB 5.6.47 and XtraDB 5.6.46-86.2 The only change is a change of the version number. In MySQL 5.6.46, the copyright comments in a number of files were changed in mysql/mysql-server@f1a006ece7521cb02f9b961e6fad04d12ddfbab3 but there was no functional change to InnoDB code. This was also reflected by XtraDB. We are not changing the copyright comments in MariaDB Server for now. Between MySQL 5.6.46 and 5.6.47, InnoDB was not changed at all. Actually, we had forgotten to update the InnoDB version number to 5.6.46. With this change, we are updating InnoDB from 5.6.45 to 5.6.47 and XtraDB from 5.6.45-86.1 to 5.6.46-86.2.	6 years ago
Sergei Petrunia	d595a91bc6	Fix a merge typo	6 years ago
Marko Mäkelä	7b70cbd838	MDEV-21499 Merge new release of InnoDB 5.7.29 to 10.2	6 years ago
Nikša Skeledžija	c25a0662b3	Bug #30499288 - GCC 9.2.1 REPORTS A NEW WARNING FOR OS_FILE_GET_PARENT_DIR - Fixed a warning visible in optimized build related to calling memcpy with length parameters larger than ptrdiff_t max. rb#23333 approved by Annamalai Gurusami <annamalai.gurusami@oracle.com>	6 years ago
Marko Mäkelä	08b0b2b6fb	MDEV-21513: Avoid some crashes in ALTER TABLE...IMPORT TABLESPACE IndexPurge::next(): Replace btr_pcur_move_to_next_user_rec() with some equivalent code that performs sanity checks without killing the server. Perform some additional sanity checks as well. This change is motivated by mysql/mysql-server@48de4d74f4d2f10cd01b129753c7dfa908cf36b5 which unnecessarily introduces storage overhead to btr_pcur_t and uses a test case that injects a fault somewhere else, not in the code path that was modified.	6 years ago
Marko Mäkelä	457ce97ef2	MDEV-21512 InnoDB may hang due to SPATIAL INDEX MySQL 5.7.29 includes the following fix: Bug #30287668 INNODB: A LONG SEMAPHORE WAIT mysql/mysql-server@5cdbb22b51cf2b35dbdf5666a251ffbec2f84dec There is no test case. It seems that the problem could occur when a spatial index is large and peculiar enough so that multiple R-tree leaf pages will have the exactly same maximum bounding rectangle (MBR). The commit message suggests that the hang can occur when R-tree non-leaf pages are being merged, which should only be possible during transaction rollback or the purge of transaction history, when the R-tree index is at least 2 levels high and very many records are being deleted. The message says that a comparison result that two spatial index node pointer records are equal will cause an infinite loop in rtr_page_copy_rec_list_end_no_locks(). Hence, we must include the child page number in the comparison to be consistent with mysql/mysql-server@2e11fe0e152e34d73579e1a9ec19aedc3f6010f6. We fix this bug in a simpler way, involving fewer code changes. cmp_rec_rec(): Renamed from cmp_rec_rec_with_match(). Assert that rec2 always resides in an index page. Treat non-leaf spatial index pages specially.	6 years ago
Marko Mäkelä	c3695b4058	MDEV-21511: Remove unnecessary code Now that we will be invoking dtuple_get_n_ext() instead of letting btr_push_update_extern_fields() update an already calculated value, it is unnecessary to calculate the n_ext upfront. row_rec_to_index_entry(), row_rec_to_index_entry_low(): Remove the output parameter n_ext.	6 years ago
Marko Mäkelä	5838b52743	MDEV-21511 Wrong estimate of affected BLOB columns in update During update, rollback, or MVCC read, we may miscalculate the number of off-page columns, and thus the size of the clustered index record. The function btr_push_update_extern_fields() is mostly redundant, because the off-page columns would also be moved by row_upd_index_replace_new_col_val(), which is invoked via row_upd_index_replace_new_col_vals(). btr_push_update_extern_fields(): Remove. This is based on mysql/mysql-server@1fa475b85d24de4b9ce2958c0eed738c221fc82c which refines a fix for a recovery bug fix mysql/mysql-server@ce0a1e85e24e48b8171f767b44330da635a6ea0a in MySQL 5.7.5. No test case was provided by Oracle. Some of the changed code is being covered by the existing test innodb.blob-crash.	6 years ago
Marko Mäkelä	3e38d15585	MDEV-21509 Possible hang during purge of history, or rollback WL#6326 in MariaDB 10.2.2 introduced a potential hang on purge or rollback when an index tree is being shrunk by multiple levels. This fix is based on mysql/mysql-server@f2c58526300c0d84837effa26d37cbd5d2694967 with the main difference that our version of the test case uses DEBUG_SYNC instrumentation on ROLLBACK, not on purge. btr_cur_will_modify_tree(): Simplify the check further. This is the actual bug fix. row_undo_mod_remove_clust_low(), row_undo_mod_clust(): Add DEBUG_SYNC instrumentation for the test case.	6 years ago
Marko Mäkelä	9cae7bdcc0	MDEV-13626: Add the WL#6326 tests	6 years ago
Jan Lindström	c4195305b2	MDEV-17062 : Test failure on galera.MW-336 Add mutex protection while we calculate required slave thread change and create them. Add error handling.	6 years ago
Jan Lindström	7e378a8d31	Test requires debug build from galera library.	6 years ago
Alexander Barkov	6f65931f88	MDEV-19906 Port show_old_temporals from MySQL 5.6 Old temporal data types (created with a pre-10.0 version of MariaDB) are now displayed with a /* mariadb-5.3 / comment in: - SHOW CREATE TABLE - DESCRIBE - INFORMATION_SCHEMA.COLUMNS.COLUMN_TYPE For example: CREATE TABLE `t1` ( `t0` datetime / mariadb-5.3 / DEFAULT NULL, `t6` datetime(6) / mariadb-5.3 */ DEFAULT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1 Note, new temporal data types are displayed without a format comment.	6 years ago
Sergei Petrunia	e709eb9bf7	Merge branch '10.2' into 10.3 # Conflicts: # mysql-test/suite/galera/r/MW-388.result # mysql-test/suite/galera/t/MW-388.test # mysql-test/suite/innodb/r/truncate_inject.result # mysql-test/suite/innodb/t/truncate_inject.test # mysql-test/suite/rpl/r/rpl_stop_slave.result # mysql-test/suite/rpl/t/rpl_stop_slave.test # sql/sp_head.cc # sql/sp_head.h # sql/sql_lex.cc # sql/sql_yacc.yy # storage/xtradb/buf/buf0dblwr.cc	6 years ago
Sergei Petrunia	b04429434a	Merge branch '10.1' into 10.2 # Conflicts: # sql/sp_head.cc # sql/sql_select.cc # sql/sql_trigger.cc	6 years ago
Sergei Golubchik	e7558d4760	fix compilation w/o perfschema followup for `3a3605f4b1`	6 years ago
Sergei Golubchik	fc5a6a28f7	compatibility with pcre2 < 10.30 * It uses stack a lot, limit the recursion depth like we used to do for pcre. * But don't do that for newer pcre2 that uses stack very little (and doesn't support limiting recursion depth anyway). * Fix tests to verify only that deep recursion doesn't crash, but ignore results and warnings (which depend on pcre2 version) * Also different pcre2 versions report different offset in error messages, take that into account.	6 years ago
Sergei Golubchik	ff5a528f26	mysqltest crashes on Debian Debian is apparently offended that pcre2-posix implements POSIX API, thus it renames all posix-compatible symbols in libpcre2-posix to have the PCRE2 prefix. But Debian doesn't do anything to pcre2posix.h header, so any unaware application will get POSIX compatible type names and function prototypes from pcre2, but actual symbols will come from libc. To remedy this enormous incongruity we have to redefine POSIX-compatible function names in pcre2posix to match Debian's hack.	6 years ago
Sergei Golubchik	1b1bf430b8	tolerate old pcre versions without PCRE2_EXTENDED_MORE flag	6 years ago
Vladislav Vaintroub	0b8b84d8d8	MDEV-21501 Innodb AIO: release IO slots early in io_callback prevent potential stalls for when all slots are used up, and all io threads are used up, and io callbacks are slow.	6 years ago
Vicențiu Ciorbaru	1bee9efcc4	MDEV-21210: main.uniques_crash-7912 tries to allocate 1TB of memory Remove the offending test case. This sort of error is hard to test in all possible corner cases and thus makes the test less valuable. The overflow error will be covered by warnings generated by the compiler, which is much more reliable in the general case.	6 years ago
Vicențiu Ciorbaru	409aba3d99	Improve documentation of Unique class * size represents the size of an element in the Unique class * full_size is used when the Unique class counts the number of duplicates stored per element. This requires additional space per Unique element.	6 years ago
Jan Lindström	bb8226deab	MDEV-21492 : Galera test sporadic failure on galera.galera_events2 Add wait condition for event creation.	6 years ago
Marko Mäkelä	bde7e0ba6e	MDEV-21500 Server hang when using simulated AIO The write-heavy test innodb_zip.wl6501_scale_1 timed out on 10.2 `60d7011c5f` for me. Out of os_aio_n_segments=6, 5 are waiting for an event in os_aio_simulated_handler(). One thread is waiting for a write to complete in buf_dblwr_add_to_batch(), but that would never happen, because nothing is waking up the simulated AIO handler threads. This hang appears to have been introduced in MySQL 5.6.12 in mysql/mysql-server@26cfde776cdf5ce61bd5cc494dfc1df28c76977f.	6 years ago
Alice Sherepa	0f0c284ec0	fix for rpl_slave_load_remove_tmpfile.test	6 years ago
Gagan Goel	f0ca9bc669	MDEV-20732 Correctly set the length of the FORMAT() result for float data type as argument.	6 years ago
Jan Lindström	a382f69e24	MDEV-21498 : wsrep.binlog_format test failed on Azure Waiting wsrep_ready is possible only if wsrep_on=ON.	6 years ago
Alexander Barkov	c32fd50952	A cleanup for MDEV-16542 Fix ALTER TABLE FORCE to upgrade temporal types Removing redundant space character after the data type comment in SHOW CREATE TABLE, so the output changes from e.g.: a TIME /* mariadb-5.3 / DEFAULT NULL to a TIME / mariadb-5.3 */ DEFAULT NULL This is a prerequisite for MDEV-19906.	6 years ago
Alexander Barkov	497ee33848	MDEV-21497 Make Field_time, Field_datetime, Field_timestamp abstract - Making classes Field_time, Field_datetime, Field_timestamp abstract - Adding instantiable Field_time0, Field_datetime0, Field_timestamp0 classes - Removing redundant cast in field_conv.cc, item_timefunc.cc, sp.cc in calls for set_time() and get_timestamp() - Replacing store_TIME() to store_timestamp() in log.cc and removing redundant cast	6 years ago
Igor Babaev	1c97cd339e	MDEV-21184 Assertion `used_tables_cache == 0' failed in Item_func::fix_fields with condition_pushdown_from_having This bug could manifest itself for queries with GROUP BY and HAVING clauses when the HAVING clause was a conjunctive condition that depended exclusively on grouping fields and at least one conjunct contained an equality of the form fld=sq where fld is a grouping field and sq is a constant subquery. In this case the optimizer tries to perform a pushdown of the HAVING condition into WHERE. To construct the pushable condition the optimizer first transforms all multiple equalities in HAVING into simple equalities. This has to be done for a proper processing of the pushed conditions in WHERE. The multiple equalities at all AND/OR levels must be converted to simple equalities because any multiple equality may refer to a multiple equality at the upper level. Before this patch the conversion was performed like this: multiple_equality(x,f1,...,fn) => x=f1 and ... and x=fn. When an equality item for x=fi was constructed both the items for x and fi were cloned. If x happened to be a constant subquery that could not be cloned the conversion failed. If the conversions of multiple equalities previously performed had succeeded then the whole condition became in an inconsistent state that could cause different failures. The solution provided by the patch is: 1. to use a different conversion rule if x is a constant multiple_equality(x,f1,...,fn) => f1=x and f2=f1 and ... and fn=f1 2. not to clone x if it's a constant. Such conversions cannot fail and besides the result of the conversion preserves the equivalence of f1,...,fn that can be used for other optimizations. This patch also made sure that expensive predicates are not pushed from HAVING to WHERE.	6 years ago
Alice Sherepa	60d7011c5f	MDEV-21360 global debug_dbug pre-test value restoration issues	6 years ago
Alice Sherepa	b7fb30e930	MDEV-21360 global debug_dbug pre-test value restoration issues	6 years ago
Alice Sherepa	451573fab1	MDEV-21360 debug_dbug pre-test value restoration issues	6 years ago
Marko Mäkelä	6a8a4c19e2	MDEV-21485 ASAN use-after-poison in dfield_get_len or Assertion `pos < index->n_def' failed The server would crash when instantly reordering the columns of a table whose all columns belong to the PRIMARY KEY.	6 years ago
Sergei Petrunia	23041af720	MDEV-21341: Fix UBSAN failures, part 8: fix error in compare_fields_by_table_order Dont assign Item_field variables to point to Item_string objects (even if we don't make any dangerous calls for them).	6 years ago
Sergei Petrunia	4635047ca1	MDEV-21341: Fix UBSAN failures, part #5 Item_cond inherits from Item_args but doesn't store its arguments as function arguments, which means it has zero arguments. Don't call memcpy in this case.	6 years ago
Jan Lindström	800d1f3010	Disable usually failing Galera tests until a real fix is found.	6 years ago
Sergei Petrunia	5e5ae51b73	MDEV-21341: Fix UBSAN failures: Issue Six (Variant #2 of the patch, which keeps the sp_head object inside the MEM_ROOT that sp_head object owns) (10.3 requires extra work due to sp_package, will commit a separate patch for it) sp_head::operator new() and operator delete() were dereferencing sp_head* pointers to memory that didn't hold a valid sp_head object (it was not created/already destroyed). This caused UBSan to crash when looking up type information. Fixed by providing static sp_head::create() and sp_head::destroy() methods.	6 years ago
Marko Mäkelä	cc3135cf83	Fix a typo in a comment	6 years ago
Daniele Sciascia	7d31321464	MDEV-19803 Long semaphore wait error on galera.MW-388 The long semaphore wait appeared to be the caused by the following pattern in the MTR test: ``` SET DEBUG_SYNC = "now SIGNAL wsrep_after_certification_continue"; SET DEBUG_SYNC = "now SIGNAL signal.wsrep_apply_cb; ``` Raising two signals, one right after another, caused one signal to overwrite the other, before the signal was consumed by the thread. This caused one thread to be stuck until the debug sync point would timeout.	6 years ago
Daniele Sciascia	2d4b6571ec	Wsrep position not updated in InnoDB after certification failures (#1432 ) A certification failure followed by a clean shutdown would cause an inconsistency between the sequence number stored in innodb and the sequence number stored in provider. This happened both in the case of local certification failure, and in the case where dummy writeset is applied. The fix consists of: - updating wsrep position after dummy writeset is delivered in `Wsrep_high_priority_service::log_dummy_write_set()` - updating wsrep position while releasing commit order in wsrep-lib side Added two tests which stress the situation where a server is shutdown after a certification failure.	6 years ago
Markus Mäkelä	5683c113b8	Use get_ident_len in heartbeat event error messages The string doesn't appear to be null-terminated when binlog checksums are enabled. This causes a corrupt binlog name in the error message when a slave is ahead of the master.	6 years ago
Marko Mäkelä	8576a7bacf	MDEV-21281 main.backup_interaction fails intermittently With MDEV-16678, some InnoDB background tasks will acquire MDL, and we must filter out such requests in the test. For this test, an alternative might have been to use wait_all_purged.inc.	6 years ago
Vladislav Vaintroub	98a67eccc5	MDEV-21327 : MDL wait notification for innodb background threadpool	6 years ago
Vladislav Vaintroub	508bc20a85	tpool - misc fixes	6 years ago
Vladislav Vaintroub	c27577a1ad	MDEV-21326 : Address TSAN warnings in tpool. 1. Fix places where data race warnings were relevant. tls_worker_data::m_state should be modified under mutex protection, since both maintainence timer and current worker set this flag. 2. Suppress warnings that are legitimate, yet harmless. Apparently, the dirty reads in waitable_task::get_ref_count() or write_slots->pending_io_count() Avoiding race entirely without side-effects here is tricky, and the effects of race is harmless. The worst thing that can happen due to race is an extra wait notification, under rare circumstances.	6 years ago

... 4 5 6 7 8 ...

188539 Commits (9ef2d29ff44de2013c95666a011b993e5c2e5674) All Branches Search

188539 Commits (9ef2d29ff44de2013c95666a011b993e5c2e5674)

All Branches