mariadb

Tree: ad6a4986eb

Author	SHA1	Message	Date
Yasufumi Kinoshita	ad6a4986eb	Bug#12400341 INNODB CAN LEAVE ORPHAN IBD FILES AROUND If we meet DB_TOO_MANY_CONCURRENT_TRXS during the execution tab_create_graph from row_create_table_for_mysql(), .ibd file for the table should be created already but was not deleted for the error handling. rb:875 approved by Jimmy Yang	14 years ago
Yasufumi Kinoshita	115f5e8551	Bug#12400341 INNODB CAN LEAVE ORPHAN IBD FILES AROUND If we meet DB_TOO_MANY_CONCURRENT_TRXS during the execution tab_create_graph from row_create_table_for_mysql(), .ibd file for the table should be created already but was not deleted for the error handling. rb:875 approved by Jimmy Yang	14 years ago
Hemant Kumar	85f874184f	Null merge from 5.1 for Bug 12872803 - 62154: FEDERATED.FEDERATED_SERVER TEST FAILS WITH RUN --REPEAT=2	14 years ago
Hemant Kumar	13b265483e	Bug#12872803 - 62154: FEDERATED.FEDERATED_SERVER TEST FAILS WITH RUN --REPEAT=2 Fixed it to work with "--repeat" option.	14 years ago
Hemant Kumar	141e89a68b	Bug#12872804 - 62155: BINLOG.BINLOG_STM_UNSAFE_WARNING FAILS WHEN RUN WITH --REPEAT=2 Fixed the testcase using timestamp logic while doing grep from the error file.	14 years ago
Hemant Kumar	b03c15413f	Bug#12872804 - 62155: BINLOG.BINLOG_STM_UNSAFE_WARNING FAILS WHEN RUN WITH --REPEAT=2 Fixed the testcase using timestamp logic while doing grep from the error file.	14 years ago
Bjorn Munch	44938d9ecc	merge 5.5-mtr => 5.5	14 years ago
Bjorn Munch	3e7bcafe0d	Followup after 13055685: Use new syntax to mask different error output in affected tests	14 years ago
Bjorn Munch	e4e61436cb	merge 5.5 => 5.5-mtr	14 years ago
Tatjana Azundris Nuernberg	ed1ba992c1	manual up-merge of Bug#11755281	14 years ago
Tatjana Azundris Nuernberg	251fa88afa	BUG#11755281/47032: ERROR 2006 / ERROR 2013 INSTEAD OF PROPER ERROR MESSAGE If init_command was incorrect, we couldn't let users execute queries, but we couldn't report the issue to the client either as it does not expect error messages before even sending a command. Thus, we simply disconnected them without throwing a clear error. We now go through the proper sequence once (without executing any user statements) so we can report back what the problem is. Only then do we disconnect the user. As always, root remains unaffected by this as init_command is (still) not executed for them. mysql-test/r/init_connect.result: We now report a proper error if init_command fails. Expect as much. mysql-test/t/init_connect.test: We now report a proper error if init_command fails. Expect as much. sql/sql_connect.cc: If init_command fails, throw an error explaining this to the user.	14 years ago
Vasil Dimov	cb80ad09da	Partial fix for Bug#11764622 57480: MEMORY LEAK WHEN HAVING 256+ TABLES Port vasil.dimov@oracle.com-20111205083046-jtgi1emlvtfnjatt from mysql-trunk	14 years ago
Vasil Dimov	a4fa485f5f	Partial fix for Bug#11764622 57480: MEMORY LEAK WHEN HAVING 256+ TABLES Port vasil.dimov@oracle.com-20111205082900-lx9om1joscejr25e from mysql-trunk	14 years ago
Vasil Dimov	93ab1d547d	Partial fix for Bug#11764622 57480: MEMORY LEAK WHEN HAVING 256+ TABLES Port vasil.dimov@oracle.com-20111205082831-7v1qu50hvd9hjr3g from mysql-trunk	14 years ago
Vasil Dimov	b7b9a4e810	Partial fix for Bug#11764622 57480: MEMORY LEAK WHEN HAVING 256+ TABLES Port vasil.dimov@oracle.com-20111205082756-wtlg8isyn4yohyny from mysql-trunk	14 years ago
Vasil Dimov	841e8ddbc5	Partial fix for Bug#11764622 57480: MEMORY LEAK WHEN HAVING 256+ TABLES Port vasil.dimov@oracle.com-20111205082626-87j5f48dq1ouk86r from mysql-trunk	14 years ago
Marko Mäkelä	1b6cb0128a	Merge mysql-5.1 to mysql-5.5.	14 years ago
Marko Mäkelä	e498a1bf65	Bug#13418934 REMOVE HAVE_PURIFY DEPENDENCES FROM INNODB InnoDB: Remove HAVE_purify, UNIV_INIT_MEM_TO_ZERO, UNIV_SET_MEM_TO_ZERO. The compile-time setting HAVE_purify can mask potential bugs. It is being set in PB2 Valgrind runs. We should simply get rid of it, and replace it with UNIV_MEM_INVALID() to declare uninitialized memory as such in Valgrind-instrumented binaries. os_mem_alloc_large(), ut_malloc_low(): Remove the parameter set_to_zero. ut_malloc(): Define as a macro that invokes ut_malloc_low(). buf_pool_init(): Never initialize the buffer pool frames. All pages must be initialized before flushing them to disk. mem_heap_alloc(): Never initialize the allocated memory block. os_mem_alloc_nocache(), ut_test_malloc(): Unused function, remove. rb:813 approved by Jimmy Yang	14 years ago
Rohit Kalhans	dcd0058723	rpl.rpl_known_bugs_detection fails on PB2 daily mysql-5.5. The rpl.rpl_known_bugs_detection fails on pb2 as warnings were found in the mysqld log file. We fix this problem by suppressing the warning.	14 years ago
Nirbhay Choubey	49d2790aff	Bug#12809202 61854: MYSQLDUMP --SINGLE-TRANSACTION --FLUSH-LOG BREAKS CONSISTENCY Post-fix for some failing tests.	14 years ago
Nirbhay Choubey	5e487124aa	Bug#12809202 61854: MYSQLDUMP --SINGLE-TRANSACTION --FLUSH-LOG BREAKS CONSISTENCY The transaction started by mysqldump gets committed implicitly when flush-log is specified along with single-transaction option, and hence can break consistency. This is because, COM_REFRESH is executed in order to flush logs and starting from 5.5 this command performs an implicit commit. Fixed by making sure that COM_REFRESH is executed before the transaction has started and not after it. Note : This patch triggers following behavioral changes in mysqldump : 1) After this patch we no longer flush logs before dumping each database if --single-transaction option is given like it was done before (in the absence of --lock-all-tables and --master-data options). 2) Also, after this patch, we start acquiring FTWRL before flushing logs in cases when only --single-transaction and --flush-logs are given. It becomes safe to use mysqldump with these two options and without --master-data parameter for backups. client/mysqldump.c: Bug#12809202 61854: MYSQLDUMP --SINGLE-TRANSACTION --FLUSH-LOG BREAKS CONSISTENCY Added logic to make sure that, if flush-log option is specified, mysql_refresh() is never executed after the transaction has started. Added verbose messages for all the executions of mysql_refresh() in order to track its invocation. mysql-test/r/mysqldump.result: Added test case for Bug#12809202. mysql-test/t/mysqldump.test: Added test case for Bug#12809202.	14 years ago
Ramil Kalimullin	a338023323	Auto-merge from mysql-5.1.	14 years ago
Ramil Kalimullin	289af2579b	Fix for bug#11758931 - 51196: SLAVE SQL: GOT AN ERROR WRITING COMMUNICATION PACKETS, ERROR_CODE: 1160 Addendum: for some queries table->in_use might be NULL - check it.	14 years ago
Ramil Kalimullin	d0ed9f437c	Auto-merge from mysq-5.1.	14 years ago
Ramil Kalimullin	790a3a46f3	Fix for bug#11758931 - 51196: SLAVE SQL: GOT AN ERROR WRITING COMMUNICATION PACKETS, ERROR_CODE: 1160 If idle FEDERATED table is evicted from the table cache when a connection to remote server is lost, query that initiated eviction may fail. If this query is executed by slave SQL thread it may fail as well. An error of close was stored in diagnostics area, which was later attributed to the statement that caused eviction. With this patch FEDERATED clears an error of close.	14 years ago
Sneha Modi	086ee89a38	Bug#11754150: A test case for Bug#6857 has been disabled in sp.test: An extra space was inserted in the code by mistake which was producing a result content mismatch.	14 years ago
Sneha Modi	805989f6ce	Bug#11754150: A TEST CASE FOR BUG#6857 IS DISABLED IN SP.TEST unix_timestamp() is implemented in this part of the code in place of current_time(). Also, since the pb2 machines may be extremely fast, instead of looping through the code, we use sleep(1.1) so that the variables t0 and t1 have different values.	14 years ago
Inaam Rana	c225712f41	merge from mysql-5.1	14 years ago
Inaam Rana	564d4a65bd	Add ChangeLog message.	14 years ago
Inaam Rana	3953b48971	Bug#11866367 FPE WHEN SETTING INNODB_SPIN_WAIT_DELAY rb://865 approved by: Jimmy Integer overflow causes division by zero.	14 years ago
Alexander Nozdrin	aff6b0fd82	A patch for Bug#13023858 - MYSQL_UPGRADE PRINTS THE ORACLE_WELCOME_COPYRIGHT_NOTICE TWICE. Fix of a merge error.	14 years ago
Sneha Modi	11fd796f8d	Bug#11754150: A TEST CASE FOR BUG#6857 IS DISABLED IN SP.TEST Unix_timestamp for time comparison has some problems...Re-using current_time for time comparison.	14 years ago
Sneha Modi	8a8155f11f	Bug#11754150: A TEST CASE FOR BUG#6857 IS DISABLED IN SP.TEST The time comparison using current_time() stored in an int variable was giving wrong results as the current_time() format as an int implementation has been changed in mysql-trunk but not in mysql-5.5. The time is stored in the format hh:mm:ss as 'time' datatype.But as an int, it is stored as hhmmss, but only on the trunk. On mysql-5.5,as an int, it is stored as hh. Hence, the current_time() function has been changed to unix_timestamp() function.	14 years ago
Joerg Bruehe	ed56fa95a0	Empty upmerge of 5.0 and 5.1 version number increases.	14 years ago
Joerg Bruehe	f2f0185a1d	Raise version number after cloning 5.5.20	14 years ago
Joerg Bruehe	b4864c8f8a	Empty upmerge of a 5.0 version number increase.	14 years ago
Joerg Bruehe	b42c3932f8	Raise version number after cloning	14 years ago
Joerg Bruehe	2d63ea643b	Raise version number after cloning	14 years ago
Chaithra Gopalareddy	7615cb0890	Bug#13344643:Format function in view looses locale information Problem description: When a view is created using function FORMAT and if FORMAT function uses locale option,definition of view saved into server doesn't contain that locale information, Ex: create table test2 (bb decimal (10,2)); insert into test2 values (10.32),(10009.2),(12345678.21); create view test3 as select format(bb,1,'sk_SK') as cc from test2; select * from test3; +--------------+ \| cc \| +--------------+ \| 10.3 \| \| 10,009.2 \| \| 12,345,678.2 \| +--------------+ 3 rows in set (0.02 sec) show create view test3 View: test3 Create View: CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `test3` AS select format(`test2`.`bb`,1) AS `cc` from `test2` character_set_client: latin1 collation_connection: latin1_swedish_ci 1 row in set (0.02 sec) Problem Analysis: The function Item_func_format::print() which prints the query string to create the view does not print the third argument (i.e the locale information). Hence view is created without locale information. Problem Solution: If argument count is more than 2 we now print the third argument onto the query string. Files changed: sql/item_strfunc.cc Function call changes: Item_func_format::print() mysql-test/t/select.test Added test case to test the bug mysql-test/r/select.result Result of the test case appended here	14 years ago
Tor Didriksen	b507df6145	Bug#13463417 63487: ANNOYING TRACE MESSAGE IN CMAKE CODE Remove it.	14 years ago
Andrei Elkin	be7fc14318	bug#13437900	14 years ago
Andrei Elkin	ed3e19aca8	Bug#13437900 - VALGRIND REPORTS A LEAK FOR REPL_IGNORE_SERVER_IDS There was memory leak when running some tests on PB2. The reason of the failure is an early return from change_master() that was supposed to deallocate a dyn-array. Actually the same bug58915 was fixed in trunk with relocating the dyn-array destruction into THD::cleanup_after_query() which can't be bypassed. The current patch backports magne.mahre@oracle.com-20110203101306-q8auashb3d7icxho and adds two optimizations: were done: the static buffer for the dyn-array to base on, and the array initialization is called precisely when it's necessary rather than per each CHANGE-MASTER as before. mysql-test/suite/rpl/t/rpl_empty_master_host.test: the test is binlog-format insensitive so it will be run with MIXED mode only. mysql-test/suite/rpl/t/rpl_server_id_ignore.test: the test is binlog-format insensitive so it will be run with MIXED mode only. sql/sql_class.cc: relocating the dyn-array destruction into THD::cleanup_after_query(). sql/sql_lex.cc: LEX.mi zero initialization is done in LEX(). sql/sql_lex.h: Optimization for repl_ignore_server_ids to base on a static buffer which size is chosen to fit to most common use cases. sql/sql_repl.cc: dyn-array destruction is relocated to THD::cleanup_after_query(). sql/sql_yacc.yy: Refining logics of Lex->mi.repl_ignore_server_ids initialization. The array is initialized once a corresponding option in CHANGE MASTER token sequence is found.	14 years ago
Georgi Kodinov	2b05ef11fc	Addendum to the fix for bug #11754011 : fixed a testcase result to include the new --slow-start-timeout option's help output	14 years ago
Georgi Kodinov	a64a25baf9	Bug#11754011: 45546: START WINDOWS SERVICE, THEN EXECUTE WHAT IS NEEDED. Added a global read-only option slow-start-timeout to control the Windows service control manager's service start timeout, that was currently hard-coded to be 15 seconds. The default of the new option is 15 seconds. The timeout can also be set to 0 (to mean no timeout applicable).	14 years ago
Annamalai Gurusami	76383243b2	Merging from mysql-5.1 to mysql-5.5.	14 years ago
Annamalai Gurusami	ad84fb5c37	Bug #13117023 : Innodb increments handler_read_key when it should not The counter handler_read_key (SSV::ha_read_key_count) is incremented incorrectly. The mysql server maintains a per thread system_status_var (SSV) object. This object contains among other things the counter SSV::ha_read_key_count. The purpose of this counter is to measure the number of requests to read a row based on a key (or the number of index lookups). This counter was wrongly incremented in the ha_innobase::innobase_get_index(). The fix removes this increment statement (for both innodb and innodb_plugin). The various callers of the innobase_get_index() was checked to determine if anybody must increment this counter (if they first call innobase_get_index() and then perform an index lookup). It was found that no caller of innobase_get_index() needs to worry about the SSV::ha_read_key_count counter.	14 years ago
Marko Mäkelä	091a2e3b0b	Merge mysql-5.1 to mysql-5.5.	14 years ago
Marko Mäkelä	3d58fd6900	Bug#13418887 ERROR IN DIAGNOSTIC FUNCTION PAGE_REC_PRINT() When printing information about a ROW_FORMAT=REDUNDANT record, pass the correct flag to rec_get_next_offs(). rb:821 approved by Jimmy Yang	14 years ago
unknown	7532976dd9	Bug #13116225 LIVE DOWNGRADE CRASHES WITH INNODB_PAGE_SIZE=4K This bug ensures that a live downgrade from an InnoDB 5.6 with WL5756 and a database created with innodb-page-size=8k or 4k will make a version 5.5 installation politely refuse to start. Instead of crashing or giving some indication about a corrupted database, it will indicate the page size difference. This patch takes only that part of the Wl5756 patch that is needed to protect against opening a tablespace that is stamped with a different page size. It also contains the change in dict_index_find_on_id_low() just in case a database with another page size is created by recompiling a pre-WL5756 InnoDB.	14 years ago
Jimmy Yang	8bb893f5c3	Fix Bug #13083023 - 60229: BROKEN COMPATIBILITY: ERROR WHILE CREATE TABLE WITH FOREIGN KEY CONSTRAI rb://844 approved by marko	14 years ago

1 2 3 4 5 ...

70078 Commits (ad6a4986eb6fef7bf0fca81670c25abd698baf5a) All Branches Search

70078 Commits (ad6a4986eb6fef7bf0fca81670c25abd698baf5a)

All Branches