mariadb

Tree: 884d22f288

Author	SHA1	Message	Date
Daniel Bartholomew	a7d02e8d24	bump the VERSION	6 years ago
Daniel Bartholomew	585e32cf3a	bump the VERSION	6 years ago
Elena Stepanova	0a891ad6a6	List of unstable tests for 10.2.31 release	6 years ago
Elena Stepanova	84d4005bad	List of unstable tests for 10.1.44 release	6 years ago
Oleksandr Byelkin	f2ccfcaca1	Merge branch '10.1' into 10.2	6 years ago
Marko Mäkelä	ac3e3e12ad	MDEV-21509: Work around occasional lost DEBUG_SYNC	6 years ago
Rafli Akmal	742c36d048	MDEV-15052: Allow sysusers and tmpfiles install for non-systemd users ..as they have their own tools that parses those files, such as opensysusers[1] that handles sysusers file and opentmpfiles[2] that handles tmpfiles.d settings Because of this. Move both sysusers and tmpfiles 'if' function outside systemd function, allowing independent install Signed-off-by: Rafli Akmal <thefallenrat@artixlinux.org> [1] - https://github.com/artix-linux/opensysusers [2] - https://github.com/OpenRC/opentmpfiles Changes done by vicentiu@mariadb.org, from original author patch: Installing sysusers and tmpfiles without checking for systemd existence means that by default, cmake will ALWAYS install these files. Our general policy is we do not install things which are not needed. However, there is a valid use case when these files are useful, as is described above. To allow this, provide an extra switch that can be enabled during configuring by doing -DINSTALL_SYSTEMD_{SYSUSERS\|TMPFILES}=True This will use the default path INSTALL_SYSTEMD_{SYSUSERS\|TMPFILES}DIR fetched from install_layout.cmake for rpm & deb based layouts respectively, or they must be overriden if the install_layout is standalone. Example: cmake . -DINSTALL_SYSTEMD_SYSUSERS=True -DINSTALL_SYSTEMD_SYSUSERSDIR=/etc/sysusers.d	8 years ago
Christian Hesse	b472bc2eba	MDEV-17028: Use descriptive file names for sysusers and tmpfiles configuration These files were installed to: ${INSTALL_SYSTEMD_SYSUSERSDIR}/sysusers.conf ${INSTALL_SYSTEMD_TMPFILESDIR}/tmpfiles.conf Instead rename the files to more descriptive file names 'mariadb.conf'.	8 years ago
Sujatha	599a06098b	MDEV-21490: binlog tests fail with valgrind: Conditional jump or move depends on uninitialised value in sql_ex_info::init Problem: ======= P1) Conditional jump or move depends on uninitialised value(s) sql_ex_info::init(char const, char const, bool) (log_event.cc:3083) code: All the following variables are not initialized. ---- return ((cached_new_format != -1) ? cached_new_format : (cached_new_format=(field_term_len > 1 \|\| enclosed_len > 1 \|\| line_term_len > 1 \|\| line_start_len > 1 \|\| escaped_len > 1))); P2) Conditional jump or move depends on uninitialised value(s) Rows_log_event::Rows_log_event(char const, unsigned int, Format_description_log_event const) (log_event.cc:9571) Code: Uninitialized values is reported for 'var_header_len' variable. ---- if (var_header_len < 2 \|\| event_len < static_cast<unsigned int>(var_header_len + (post_start - buf))) P3) Conditional jump or move depends on uninitialised value(s) Table_map_log_event::pack_info(Protocol) (log_event.cc:11553) code:'m_table_id' is uninitialized. ---- void Table_map_log_event::pack_info(Protocol protocol) ... size_t bytes= my_snprintf(buf, sizeof(buf), "table_id: %lu (%s.%s)", m_table_id, m_dbnam, m_tblnam); Fix: === P1 - Fix) Initialize cached_new_format,field_term_len, enclosed_len, line_term_len, line_start_len, escaped_len members in default constructor. P2 - Fix) "var_header_len" is initialized by reading the event buffer. In case of an invalid event the buffer will contain invalid data. Hence added a check to validate the event data. If event_len is smaller than valid header length return immediately. P3 - Fix) 'm_table_id' within Table_map_log_event is initialized by reading data from the event buffer. Use 'VALIDATE_BYTES_READ' macro to validate the current state of the buffer. If it is invalid return immediately.	6 years ago
Sergei Golubchik	26a46444b4	don't run main.ssl_system_ca in --embedded this test needs a server and tries to connect with $MYSQL to it	6 years ago
Alexey Botchkov	683a49889c	MENT-464 ASAN MTR quick test - some failures to be investigated. PCRE reports small frame size working with ASAN, so the test has to be ready for the minimlas possible size.	6 years ago
Marko Mäkelä	7aa443ca7d	Remove an unused tokuvalgrind script This is the only symlink in the repository. Symlinks can cause trouble when using file systems or operating systems that do not support them. Also remove the unused file DartConfig.cmake that refers to the script.	6 years ago
Marko Mäkelä	1d12bff42c	MDEV-20775: page_zip_validate() failure due to AUTO_INCREMENT cmake -DWITH_INNODB_EXTRA_DEBUG:BOOL=ON was broken ever since commit `8777458a6e` (MDEV-6076 Persistent AUTO_INCREMENT for InnoDB). There is a race condition between page reads that call page_zip_validate() (while holding clustered index root page S-latch) and writes that update PAGE_ROOT_AUTO_INC (with buf_block_t::lock SX-latch, compatible with S-latch). page_zip_validate_low(): Skip the PAGE_ROOT_AUTO_INC field on clustered index root pages in order to avoid false positives.	6 years ago
Vlad Lesin	7c166e68aa	MDEV-14183: aria_pack segfaults in compress_maria_file Post-push fix. aria_pack_mdev14183 test is unstable. The fix is the following: 1. Disable the test for embedded server. 2. Create non-"transactional" Aria table in the test, as aria_pack does not support "transactional" Aria tables.	6 years ago
Sergei Golubchik	1f9a0437da	new C/C and --ssl-verify-server-cert tests tests for --ssl-verify-server-cert with system CA and with incorrect hostname	6 years ago
Sergei Golubchik	8eec2d61fc	MDEV-21249 MariaDB 10.3.10 When referring to bigint to generate timestamp data in the virtual generated column, the value of the generated column does not change when the time zone changes FROM_UNIXTIME() depends on @@time_zone, so it's VCOL_SESSION_FUNC	6 years ago
Vlad Lesin	4e7f3fb833	MDEV-14183: aria_pack segfaults in compress_maria_file Column definition order in st_maria_share::columndef can differ from order of fields in record(see also st_maria_share::column_nr, st_maria_columndef::column_nr, _ma_column_nr_write(), _ma_column_nr_read()). This was not taken into account in aria_pack tool. The fix is to initialize elements of HUFF_COUNTS array in the correct order.	6 years ago
Alice Sherepa	90e7e6783b	MDEV-21360 save/restore debud_dbug instead of total reset at the end of the test	6 years ago
Alice Sherepa	10a5e1eccb	MDEV-21360 save/restore debud_dbug instead of total reset at the end of the test	6 years ago
Sergei Golubchik	8870f18e1d	MDEV-17292 Package the pam_user_map module	6 years ago
Sergei Golubchik	42049f9d39	cleanup: simplify install_layout.cmake	6 years ago
Julius Goryavsky	982294ac16	MDEV-17601: MariaDB Galera does not expect 'mbstream' as streamfmt Setting "streamfmt=mbstream" in the "[sst]" section causes SST to fail because the format automatically switches to 'tar' by default (insead of mbstream). To fix this, we need to add mbstream to the list of valid values for the format, making it synonymous with xbstream. This must be done both in the SST script and when parsing the options of the corresponding utilities.	6 years ago
Oleksandr Byelkin	a5b38151c0	new version CC 3.1	6 years ago
Oleksandr Byelkin	3a1716a7e7	Merge branch '10.1' into 10.2	6 years ago
Oleksandr Byelkin	d07664498b	Merge remote-tracking branch 'connect/10.2' into 10.2	6 years ago
Jan Lindström	90d39f2f91	MDEV-21532 : galera.galera_rsu_drop_pk MTR failed: Result content mismatch Add wait conditions to make sure correct number of rows have been replicated.	6 years ago
Julius Goryavsky	578b6ba02a	MDEV-19457: sys_vars.wsrep_provider_basic failed in buildbot If the initialization of the wsrep provider failed, in some cases the internal variable wrep_inited indicating that the initialization has already been completed is still set to "1", which then leads to confusion in the initialization status. To solve the problem, we should set this variable to "1" only if the wsrep provider initialization really completed successfully. An earlier issue has already been fixed for branch 10.4, and this patch contains a fix for earlier versions (where Galera 3.x is used).	6 years ago
Marko Mäkelä	ceffabc421	Enable tests for --embedded	6 years ago
Marko Mäkelä	e47b780286	MDEV-13626: Work around DEBUG_SYNC timeouts	6 years ago
Oleksandr Byelkin	7993f893b8	Merge branch 'merge-tokudb-5.6' into 10.1	6 years ago
Oleksandr Byelkin	6cb208107e	5.6.46-86.2	6 years ago
Oleksandr Byelkin	10eacd5ff7	Merge branch 'merge-perfschema-5.6' into 10.1	6 years ago
Oleksandr Byelkin	3aff3f3679	5.6.47	6 years ago
Oleksandr Byelkin	5ce6ec3fb5	Merge remote-tracking branch 'connect/10.1' into 10.1	6 years ago
Oleksandr Byelkin	f31bf6f094	Merge branch '5.5' into 10.1	6 years ago
Sergei Golubchik	4d1c1b23e1	Bug#29630767 - USE OF UNINITIALIZED VALUE IN LIBMYSQL (CLIENT.CC FUNCTION RUN_PLUGIN_AUTH)	6 years ago
Maheedhar PV	49b9ce15ef	Bug#30194841 INSERT ON DUPLICATE KEY UPDATE UPDATES THE WRONG ROW test case only	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
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
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

1 2 3 4 5 ...

183205 Commits (884d22f28884e1decced1dee9c69ddcb25002ed1) All Branches Search

183205 Commits (884d22f28884e1decced1dee9c69ddcb25002ed1)

All Branches