mariadb

Tree: 0ed57e34c7

Author	SHA1	Message	Date
Vicențiu Ciorbaru	0ed57e34c7	MDEV-7025 ANALYZE SELECT/INSERT/UPDATE/DELETE from a view does not check access permissions on the view Added access checking for the ANALYZE statement command.	11 years ago
Jan Lindström	c8035da9b8	Add more information if page state is not correct.	11 years ago
Sergei Golubchik	f7d196bb2e	32bit fix	11 years ago
Sergei Golubchik	e2de804491	Merge branch '10.1' into bb-10.1-serg	11 years ago
Sergei Petrunia	2288b84df4	MDEV-7679: ANALYZE crashes when printing WHERE when no default db Fix Item_ident::print() to work when there is no current database	11 years ago
Sergei Petrunia	66ad265f3b	MDEV-7674: ANALYZE shows r_rows=0 Change r_rows to be double	11 years ago
Sergei Golubchik	5bff6c5d57	bison warning: clash on default action: <NONE> != <object_ddl_options>	11 years ago
Sergei Golubchik	6d8b74dd07	add a test for drop trigger under --read-only	11 years ago
Sergei Golubchik	18feb62fee	MDEV-6819 st_mysql_show_var::value should be void* not char*	11 years ago
Sergei Golubchik	20cacb0064	fix a crash of innodb.innodb_mutexes,innodb_plugin add forgotten initialization of the mutex name	11 years ago
Sergei Golubchik	2db62f686e	Merge branch '10.0' into 10.1	11 years ago
Sergei Golubchik	d61573d3e5	fix connect.json_udf test for static builds	11 years ago
Sergei Golubchik	c0af8213fe	MDEV-7669 tmp_table_count-7586 fails in ps and embedded disable a broken test, pending a proper fix	11 years ago
Sergei Golubchik	5f510a9175	Merge branch '5.5' into 10.0	11 years ago
Sergei Golubchik	17a37796e1	after innodb/xtradb merge: use the correct visibility for internal functions otherwise innodb plugin might invoke xtradb function with the same name, and that might crash (./mtr --emb innodb.strict_mode)	11 years ago
Sergei Golubchik	d7d19071d2	MDEV-6838 Using too big key for internal temp tables update test results after the fix	11 years ago
Sergei Golubchik	12d87c3ba5	MDEV-7659 buildbot may leave stale mysqld safe_process puts its children (mysqld, in this case) into a separate process group, to be able to kill it all at once. buildslave kills mtr's process group when it loses connection to the master. result? buildslave kills mtr and safe_process, but leaves stale mysqld processes in their own process groups. fix: put safe_process itself into a separate process group, then buildslave won't kill it and safe_process will kill mysqld'd and itself when it will notice that the parent mtr no longer exists.	11 years ago
Jan Lindström	206b111b11	MDEV-7672: Crash creating an InnoDB table with foreign keys Analysis: after a red-black-tree lookup we use node withouth checking did lookup succeed or not. This lead to situation where NULL-pointer was used. Fix: Add additional check that found node from red-back-tree is valid.	11 years ago
Sergey Vojtovich	e13459a11e	MDEV-7148 - Recurring: InnoDB: Failing assertion: !lock->recursive Re-applied lost in the merge revision: commit `ed313e8a92` Author: Sergey Vojtovich <svoj@mariadb.org> Date: Mon Dec 1 14:58:29 2014 +0400 MDEV-7148 - Recurring: InnoDB: Failing assertion: !lock->recursive On PPC64 high-loaded server may crash due to assertion failure in InnoDB rwlocks code. This happened because load order between "recursive" and "writer_thread" wasn't properly enforced.	11 years ago
Jan Lindström	f66fbe8ce0	MDEV-7578 :Slave is ~10x slower to execute set of statements compared to master when using RBR Analysis: On master when executing (single/multi) row INSERTs/REPLACEs InnoDB fallback to old style autoinc locks (table locks) only if another transaction has already acquired the AUTOINC lock. Instead on slave as we are executing log_events and sql_command is not correctly set, InnoDB does not use new style autoinc locks when it could. Fix: Use new style autoinc locks also when thd_sql_command(user_thd) == SQLCOM_END i.e. this is RBR event.	11 years ago
Kristian Nielsen	7dee7a036a	GTID: Add missing test of reconnecting into out-of-order binlog.	11 years ago
Jan Lindström	143f5d9172	MDEV-7061: Augment innochecksum to give insight of fragmentation Merged `615dd07d90` from https://github.com/facebook/mysql-5.6/ authored by rongrong. Removed C++11 requirement by using std::map instead of std::unordered_set. Add analysis to leaf pages to estimate how fragmented an index is and how much benefit we can get out of defragmentation.	11 years ago
Kristian Nielsen	2e4dc5a370	after-merge fixes	11 years ago
Kristian Nielsen	95d7208859	Merge MDEV-6589 and MDEV-6403 into 10.1. Conflicts: sql/log.cc sql/rpl_rli.cc sql/sql_repl.cc	11 years ago
Kristian Nielsen	3ef0b9b235	Merge MDEV-6589 and MDEV-6403 into 10.0.	11 years ago
Kristian Nielsen	78c74dbe30	MDEV-6403: Temporary tables lost at STOP SLAVE in GTID mode if master has not rotated binlog since restart The binlog contains specially marked format description events to mark when a master restart happened (which could have caused temporary tables to be silently dropped). Such events also cause slave to close temporary tables. However, there was a bug that if after this, slave re-connects to the master in GTID mode, the master can send an old format description event again. If temporary tables are closed when such event is seen for the second time, it might drop temporary tables created after that event, and cause replication failure. With this patch, the restart flag of the format description event is cleared by the master when it is sent to the slave in a subsequent connection, to avoid the errorneous temp table close.	11 years ago
Kristian Nielsen	ad0d203f2e	MDEV-6589: Incorrect relay log start position when restarting SQL thread after error in parallel replication The problem occurs in parallel replication in GTID mode, when we are using multiple replication domains. In this case, if the SQL thread stops, the slave GTID position may refer to a different point in the relay log for each domain. The bug was that when the SQL thread was stopped and restarted (but the IO thread was kept running), the SQL thread would resume applying the relay log from the point of the most advanced replication domain, silently skipping all earlier events within other domains. This caused replication corruption. This patch solves the problem by storing, when the SQL thread stops with multiple parallel replication domains active, the current GTID position. Additionally, the current position in the relay logs is moved back to a point known to be earlier than the current position of any replication domain. Then when the SQL thread restarts from the earlier position, GTIDs encountered are compared against the stored GTID position. Any GTID that was already applied before the stop is skipped to avoid duplicate apply. This patch should have no effect if multi-domain GTID parallel replication is not used. Similarly, if both SQL and IO thread are stopped and restarted, the patch has no effect, as in this case the existing relay logs are removed and re-fetched from the master at the current global @@gtid_slave_pos.	11 years ago
Sergey Vojtovich	f4f37533a0	Replaced lf-hash element_size hack with initializer function.	11 years ago
Sergey Vojtovich	5c6aa4dea0	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Replaced hash with lock-free hash.	11 years ago
Sergey Vojtovich	d9e3a9f20e	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Extended lf-hash implementation to accept user defined hash function.	11 years ago
Sergey Vojtovich	9c8165fdb4	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Added initializer callback to lf-hash. Needed to initialize properly non-POD types.	11 years ago
Sergey Vojtovich	f5bd1d0126	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Simplified MDL_object_lock and MDL_scoped_lock dichotomy so that they can be stored in LF_HASH. This was done by moving out their differences to a MDL_lock_strategy structure which is referenced from the MDL_lock object by pointer.	11 years ago
Sergey Vojtovich	f475a7f949	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Replaced m_ref_usage, m_ref_release, m_is_destroyed and m_version with single m_state, which is updated atomically. Needed to get rid of MDL_map::m_mutex.	11 years ago
Sergey Vojtovich	ecd3ff9f24	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Removed MDL map partitions. Won't be needed when this MDEV is implemented.	11 years ago
Sergey Vojtovich	903160ef59	MDEV-6089 - MySQL WL#7305 "Improve MDL scalability by using lock-free hash" Removed MDL objects cache. Won't be needed when this MDEV is implemented.	11 years ago
Alexander Barkov	87b0cc9912	MDEV-7286 TRIGGER: CREATE OR REPLACE, CREATE IF NOT EXISTS Based on the patch by Sriram Patil, made under terms of GSoC 2014.	11 years ago
Alexander Barkov	a7ed8523e3	Adding a shared include file ctype-mb.ic and removing a number of very similar copies of my_well_formed_len_xxx(), implemented for big5, cp932, euckr, eucjpms, gb2312m gbk, sjis, ujis.	11 years ago
Sergei Golubchik	d8c1165c28	fix failing innodb.innodb-page_encryption_log_encryption again adjust suppression rules after warning message format change	11 years ago
Sergei Golubchik	e33b48ae8b	Merge remote-tracking branch 'origin/10.0' into 10.0	11 years ago
Sergei Golubchik	c06c465a96	10.0-connect merge	11 years ago
Alexander Barkov	b1b6101af2	A preparatory patch for MDEV-6566. Adding a new virtual function MY_CHARSET_HANDLER::copy_abort(). Moving character set specific code into the correspoding implementations (for simple, multi-byte and mbmaxlen>1 character sets).	11 years ago
Jan Lindström	7047bef1ef	Use standard InnoDB error mechanism on compression and encryption error messages.	11 years ago
Olivier Bertrand	b9a9b82f9e	- Make json_udf test work on Windows modified: storage/connect/mysql-test/connect/t/json_udf.inc	11 years ago
Olivier Bertrand	5f4909b31d	- Making json_udf test working on linux added: storage/connect/mysql-test/connect/t/json_udf.inc modified: storage/connect/mysql-test/connect/r/json_udf.result storage/connect/mysql-test/connect/t/json_udf.test	11 years ago
Olivier Bertrand	34c89597ef	- Remove a signed/unsigned warning. modified: storage/connect/jsonudf.cpp	11 years ago
Olivier Bertrand	5c8862ee19	- Fix crash when Json_Value was called without arguments. Correct memory calculation in Serialize. Correct some UDF's messages. Add and modify the json tests removed: storage/connect/mysql-test/connect/std_data/biblio.jsn storage/connect/mysql-test/connect/std_data/expense.jsn storage/connect/mysql-test/connect/std_data/mulexp3.jsn storage/connect/mysql-test/connect/std_data/mulexp4.jsn storage/connect/mysql-test/connect/std_data/mulexp5.jsn added: storage/connect/mysql-test/connect/r/json_udf.result storage/connect/mysql-test/connect/std_data/biblio.json storage/connect/mysql-test/connect/std_data/expense.json storage/connect/mysql-test/connect/std_data/mulexp3.json storage/connect/mysql-test/connect/std_data/mulexp4.json storage/connect/mysql-test/connect/std_data/mulexp5.json storage/connect/mysql-test/connect/t/json_udf.test modified: storage/connect/json.cpp storage/connect/jsonudf.cpp storage/connect/mysql-test/connect/r/json.result storage/connect/mysql-test/connect/t/json.test	11 years ago
Sergei Golubchik	1f1f977167	Fix test failing when file_key_management_plugin doesn't load * remove useless suppressions from the test file, when a plugin doesn't load, the file isn't executed anyway * add the suppression to mysql-test-run.pl instead	11 years ago
Sergei Golubchik	c3f80a2bff	fix new innodb warnings to use the standard innodb warning syntax	11 years ago
Olivier Bertrand	d862d7c049	- Implement random access to ODBC tables modified: storage/connect/odbconn.cpp storage/connect/odbconn.h - Fix get proper length of ODBC DECIMAL column in discovery modified: storage/connect/ha_connect.cc storage/connect/mysql-test/connect/r/odbc_oracle.result - Implement random access to JSON tables modified: storage/connect/tabjson.cpp storage/connect/tabjson.h - Fix MDEV-7636 modified: storage/connect/tabutil.cpp	11 years ago
Vicențiu Ciorbaru	45b6edb158	MDEV-6838: Using too big key for internal temp tables This bug manifests due to wrong computation and evaluation of keyinfo->key_length. The issues were: * Using table->file->max_key_length() as an absolute value that must not be reached for a key, while it represents the maximum number of bytes possible for a table key. * Incorrectly computing the keyinfo->key_length size during KEY_PART_INFO creation. The metadata information regarding the key such the field length (for strings) was added twice.	11 years ago

1 2 3 4 5 ...

164870 Commits (0ed57e34c76ffa5e457e1abb402ada6352fb52b2) All Branches Search

164870 Commits (0ed57e34c76ffa5e457e1abb402ada6352fb52b2)

All Branches