mariadb

Tree: 0903a40d09

Author	SHA1	Message	Date
unknown	0903a40d09	bMDEV-4906: When event apply fails, next SQL thread start errorneously commits the failing GTID to gtid_slave_pos When a GTID event is executed, we remember the contained GTID position so that when we have applied the entire event group we can commit it to gtid_slave_pos. However, if the event group fails to apply due to some error and the SQL thread aborts, the code did not correctly clear the remembered GTID. Thus, when SQL thread was restarted, the old GTID of the failing event group was incorrectly updated to gtid_slave_pos when the initial rotate event was executed, corrupting the GTID position.	12 years ago
unknown	35b2883643	merge 5.5 -> 10.0-base	12 years ago
unknown	dafa458262	mysql-test/r/func_set.result:	12 years ago
Igor Babaev	7c85205d19	Fixed bug mdev-4918. The function SELECT_LEX::mark_const_derived() must take into account that in DELETE ... RETURNING join == NULL.	12 years ago
unknown	f0deff867a	MDEV-4820: Empty master does not give error for slave GTID position that does not exist in the binlog The main bug here was the following situation: Suppose we set up a completely new master2 as an extra multi-master to an existing slave that already has a different master1 for domain_id=0. When the slave tries to connect to master2, master2 will not have anything that slave requests in domain_id=0, but that is fine as master2 is supposedly meant to serve eg. domain_id=1. (This is MDEV-4485). But suppose that master2 then actually starts sending events from domain_id=0. In this case, the fix for MDEV-4485 was incomplete, and the code would fail to give the error that the position requested by the slave in domain_id=0 was missing from the binlogs of master2. This could lead to lost events or completely wrong replication. The patch for this bug fixes this issue. In addition, it cleans up the code a bit, getting rid of the fake_gtid_hash in the code. And the error message when slave and master have diverged due to alternate future is clarified, as requested in the bug description.	12 years ago
Alexander Barkov	b59738a598	Merge from 5.3 modified: mysql-test/r/dyncol.result mysql-test/r/type_time.result mysql-test/t/dyncol.test mysql-test/t/type_time.test mysys/ma_dyncol.c sql/item.cc sql/item_func.cc pending merges: Alexander Barkov 2013-08-12 MDEV-4652 Wrong result for CONCAT(GREATEST(T... sanja@montyprogr... 2013-08-01 MDEV-4811 Assertion `offset < 0x1f' f...	12 years ago
Alexander Barkov	f1b4718ec8	MDEV-4652 Wrong result for CONCAT(GREATEST(TIME('00:00:01'),TIME('00:00:00'))	12 years ago
Sergei Golubchik	b718dc449b	mysql --skip-column-names flag should not affect alignment of field values, set num_flag[] unconditionally, not under "if (column_names)" http://ronaldbradford.com/blog/unexplained-trivial-mysql-behavior-2013-08-02/	12 years ago
Alexander Barkov	cafe9d13f6	Merge from 5.3 pending merges: Alexander Barkov 2013-08-08 MDEV-4653 Wrong result for CONVERT_TZ(TIME('...	12 years ago
Alexander Barkov	e9db0da787	MDEV-4653 Wrong result for CONVERT_TZ(TIME('00:00:00'),'+00:00','+7:5')	12 years ago
Alexander Barkov	62484d2e23	Merge from 5.3 pending merges: Alexander Barkov 2013-08-08 MDEV-4512 Valgrind warnings in my_long10_to_...	12 years ago
Alexander Barkov	e6a6f653a9	MDEV-4512 Valgrind warnings in my_long10_to_str_8bit on INTERVAL and DATE_ADD with incorrect types Fixing a typo: bit AND (&) was erroneously used instead of logical AND (&&)	12 years ago
Igor Babaev	f08946c037	Merge	12 years ago
Igor Babaev	86d62605e8	MWL#205 DELETE with result set (mdev-3814) Includes all post-review fixes as well.	12 years ago
unknown	220623572d	Fix possible race condition in Query cache.	12 years ago
Sergey Petrunya	96340a405a	Automatic merge	12 years ago
Elena Stepanova	f2b84e305c	Fixes for storage_engine tests diverged from the main line	12 years ago
Sergey Petrunya	c98cd2c816	Update test results after fix for MDEV-4687	12 years ago
Elena Stepanova	b9f61c14b7	Deliberate change in behavior introduced in MySQL 5.5.31 along with the partitioning enhancement for Bug#14521864	12 years ago
Elena Stepanova	32e56e7e14	The test was non-deterministic while choosing an alternative storage engine	12 years ago
Elena Stepanova	f596d28df6	Deliberate change in behavior introduced along with the fix for MDEV-4310	12 years ago
unknown	04fd2f18cb	MDEV-4811 Assertion `offset < 0x1f' fails in type_and_offset_store on COLUMN_ADD MDEV-4812 Valgrind warnings (Invalid write) in dynamic_column_update_many on COLUMN_ADD Fixed problem of working on wrong data (do not allow offset to out of string length).	12 years ago
Sergey Petrunya	04684b7709	MDEV-4817: Optimizer fails to optimize expression of the form 'FOO' IS NULL - Modify the way Item_cond::fix_fields() and Item_cond::eval_not_null_tables() calculate bitmap for Item_cond_or::not_null_tables(): if they see a "... OR inexpensive_const_false_item OR ..." then the item can be ignored. - Updated test results. There can be more warnings produced since parts of WHERE are evaluated more times.	12 years ago
Sergey Petrunya	6fb1786584	Automatic merge	12 years ago
Vladislav Vaintroub	3ef0157daa	MDEV-4815 - allow multiple mysql_server_init() / mysql_server_end() in the same process, for embedded library. - Reset static variables that are used to signal "init done" for DBUG, in dbug_end() - Set string server variables to NULL after memory for the value is freed - avoids double free() - fix DBUG_ASSERTs that happened during reinitialization.	12 years ago
Sergey Petrunya	9a780a59d5	MDEV-4687: impossible where with < operation, but =-5 return one row - Let _ma_record_pos() set SEARCH_PART_KEY when doing a search on a prefix of a [unique] key. Otherwise, _ma_search_pos() would find the first key equal to search key, and assume it is also the last one, which will make a wrong estimate of key's position. A wrong key position may cause min_pos > max_pos and records_in_range() will return 0, which will make the optimizer think it's an impossible range while in fact it is not.	13 years ago
unknown	9e13011efb	Revert reverted patch (as workaround) to have no problem with ongoing fix.	13 years ago
unknown	07099b7021	Fix of using uninitialized variadle.	13 years ago
Sergei Golubchik	97e640b9ae	5.5 merge	13 years ago
unknown	c7973615e7	Revert of marko.makela@oracle.com-20130430103950-j353faze84zzk9xf for xtradb (fix of http://bugs.mysql.com/bug.php?id=69623)	13 years ago
unknown	66ec79fc87	Fix for MDEV-4219 A simple select query returns random data (upstream bug#68473) In the case of loose scan used as input for order by, end_send() didn't detect correctly that a loose scan was used, and didn't copy the non-aggregated fields from the temp table used for ORDER BY. The fix uses the fact that the quick select used for sorting is attached to JOIN::pre_sort_join_tab instead of JOIN::join_tab.	13 years ago
Sergei Golubchik	a5b534a08e	merge Percona-Server-5.5.32-rel31.0.tar.gz	13 years ago
Sergei Golubchik	005c7e5421	mysql-5.5.32 merge	13 years ago
Sergei Golubchik	b9f220b45a	5.3 merge	13 years ago
Sergei Golubchik	6bd24f07d4	Percona-Server-5.5.32-rel31.0.tar.gz	13 years ago
Sergey Petrunya	67e5b7945d	Automatic merge	13 years ago
Sergey Petrunya	5c0fa3ad8f	Update test results after the last cset.	13 years ago
Sergey Petrunya	947c2bdbc0	MDEV-4782: Valgrind warnings (Conditional jump or move depends on uninitialised value) with InnoDB, semijoin - in sub_select(): don't call table->file->position() when reading the first record produced an error.	13 years ago
Sergey Petrunya	47c1b04079	MDEV-4778: Incorrect results from Aria/MyISAM SELECT using index with prefix length on TEXT column Backport the fix olav.sandstaa@sun.com-20101102184747-qfuntqwj021imy9r: "Fix for Bug#52660 Perf. regr. using ICP for MyISAM on range queries on an index containing TEXT" (together with further fixes in that code) into MyISAM and Aria.	13 years ago
Sergey Petrunya	9651a6f574	mdev-4173: Wrong result (extra row) with semijoin=on, joins in outer query, LEFT JOIN in the subquery Apply the patch from Patryk Pomykalski: - create_internal_tmp_table_from_heap() will now return information whether the last row that we tried to write was a duplicate row. (mysql-5.6 also has this change)	13 years ago
Sergei Golubchik	8de120e2b9	5.2 merge	13 years ago
Sergey Petrunya	716a49a19e	MDEV-4536, MDEV-4042 - Make JOIN::cleanup(true) also work correctly when the query is KILLed after join optimization was started but before a query plan was produced	13 years ago
Sergey Petrunya	e8b0b51966	MDEV-4042: Assertion `table->key_read == 0' fails in close_thread_table on EXPLAIN MDEV-4536: ...sql/sql_base.cc:1598: bool close_thread_table(THD, TABLE*): Assertion - Make JOIN::cleanup(full=true) always free join optimization tabs.	13 years ago
Sergey Petrunya	a0de3e0485	MDEV-4556 Server crashes in SEL_ARG::rb_insert with index_merge+index_merge_sort_union, FORCE INDEX - merge_same_index_scans() may put the same SEL_ARG tree in multiple result plans. make it call incr_refs() on the SEL_ARG trees that it does key_or() on, because key_or(sel_arg_tree_1, sel_arg_tree_2) call may invalidate SEL_ARG trees pointed by sel_arg_tree_1 and sel_arg_tree_2.	13 years ago
unknown	2f6a2494a5	MDEV-4708: GTID strict mode doesn't work on a database with purged binlogs When a new master is provisioned that does not have any old binlogs, the @@gtid_slave_pos is used to know where in the GTID history the provisioning happened. A slave is allowed to connect at the point of this value of @@gtid_slave_pos, even if that GTID is not in the binlogs on the new master. The code to handle this case when the binlog on the newly provisioned master is completely empty was just wrong (couple of typos). Clearly it had never been tested ... :-/	13 years ago
unknown	1e43277838	MDEV-4708: GTID strict mode doesn't work on a database with purged binlogs When a new master is provisioned that does not have any old binlogs, the @@gtid_slave_pos is used to know where in the GTID history the provisioning happened. A slave is allowed to connect at the point of this value of @@gtid_slave_pos, even if that GTID is not in the binlogs on the new master. But --gtid-strict-mode did not correctly handle this case. When strict mode was enabled, an attempt to connect at the position would cause an error about holes in the binlog, which is not correct. This patch adds a hash of GTIDs that need to be treated specially by GTID strict mode to deal correctly with this case.	13 years ago
Alexander Barkov	c51ed128b0	Merge from 5.3	13 years ago
Vladislav Vaintroub	6bef652d91	MDEV-4409 - Fix deadlock in MySQL key cache code, that can happen if there is a key cache resize running in parallel with an update. If there is a key cache resize,a thread writing to key cache, will pause waiting until resize finishes. However this thread is won't be woken, because resize does not signaling waiters anymore. This is a regression introduced in WL#86(segmented MyISAM key cache) The fix is to unconditionally release threads waiting on resize_queue when resize finishes, as in pre-WL#86 code.	13 years ago
Alexander Barkov	8a732d5a5e	Merge from 5.2 modified: mysql-test/suite/plugins/r/fulltext_plugin.result mysql-test/suite/plugins/t/fulltext_plugin.test plugin/fulltext/plugin_example.c sql/sql_show.cc pending merges: Alexander Barkov 2013-07-09 [merge] Merge from 5.1 Sergei Golubchik 2013-07-06 Bug #69682 - mysqld crashes after uninst... Sergei Golubchik 2013-05-24 MDEV-4575 MySQL client doesn't strip off...	13 years ago
Alexander Barkov	762d3cb8ed	Merge from 5.1 modified: mysql-test/suite/plugins/r/fulltext_plugin.result mysql-test/suite/plugins/t/fulltext_plugin.test plugin/fulltext/plugin_example.c sql/sql_show.cc pending merges: Sergei Golubchik 2013-07-06 Bug #69682 - mysqld crashes after uninstall ... Sergei Golubchik 2013-05-24 MDEV-4575 MySQL client doesn't strip off...	13 years ago

1 2 3 4 5 ...

77867 Commits (0903a40d09a98bb482d2d53530d60eb539753443) All Branches Search

77867 Commits (0903a40d09a98bb482d2d53530d60eb539753443)

All Branches