mariadb

Commit Graph

Author	SHA1	Message	Date
Sergey Vojtovich	0212e73613	Merge of innodb-zip-ss6129 snapshot.	16 years ago
Sergey Vojtovich	7c4cae75b8	Clean-up after applying innodb-zip-ss6129 snapshot: - re-enabled main.innodb_bug44369; - re-enabled main.innodb_bug47777; - re-enabled innodb.innodb_information_schema.	16 years ago
Jorgen Loland	bec35067d3	Bug#48177 - SELECTs with NOT IN subqueries containing NULL values return too many records WHERE clauses with "outer_value_list NOT IN subselect" were handled incorrectly if the outer value list contained multiple items where at least one of these could be NULL. The first outer record with NULL value was handled correctly, but if a second record with NULL value existed, the optimizer would choose to reuse the result it got on the last execution of the subselect. This is incorrect if the outer value list has multiple items. The fix is to make Item_in_optimizer::val_int (in item_cmpfunc.cc) reuse the result of the latest execution for NULL values only if all values in the outer_value_list are NULL. mysql-test/r/subselect3.result: Added test for BUG#48177 mysql-test/t/subselect3.test: Added test for BUG#48177 sql/item_cmpfunc.cc: Make Item_in_optimizer::val_int (in item_cmpfunc.cc) reuse the result of the latest execution for NULL values only if all values in the outer_value_list are NULL.	16 years ago
Sergey Vojtovich	f24dd341da	Applying InnoDB plugin snashot Detailed revision comments: r6126 \| vasil \| 2009-10-30 10:36:07 +0200 (Fri, 30 Oct 2009) \| 45 lines branches/zip: Merge r6112:6125 from branches/5.1: (skipping r6122 and r6123, Jimmy says these are already present and need not be merged): ------------------------------------------------------------------------ r6122 \| jyang \| 2009-10-30 05:18:38 +0200 (Fri, 30 Oct 2009) \| 7 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc M /branches/5.1/mysql-test/innodb_bug44369.result M /branches/5.1/mysql-test/innodb_bug44369.test M /branches/5.1/mysql-test/innodb_bug46000.result M /branches/5.1/mysql-test/innodb_bug46000.test branches/5.1: Chnage WARN_LEVEL_ERROR to WARN_LEVEL_WARN for push_warning_printf() call in innodb. Fix Bug#47233: Innodb calls push_warning(MYSQL_ERROR::WARN_LEVEL_ERROR) rb://170 approved by Marko. ------------------------------------------------------------------------ r6123 \| jyang \| 2009-10-30 05:43:06 +0200 (Fri, 30 Oct 2009) \| 8 lines Changed paths: M /branches/5.1/os/os0proc.c branches/5.1: In os_mem_alloc_large(), if we fail to attach the shared memory, reset memory pointer ptr to NULL, and allocate memory from conventional pool. This is a port from branches/zip. Bug #48237 Error handling in os_mem_alloc_large appears to be incorrect rb://198 Approved by: Marko ------------------------------------------------------------------------ r6125 \| vasil \| 2009-10-30 10:31:23 +0200 (Fri, 30 Oct 2009) \| 4 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc branches/5.1: White-space fixup. ------------------------------------------------------------------------	16 years ago
Sergey Vojtovich	f73596ab16	Applying InnoDB plugin snashot Detailed revision comments: r6121 \| sunny \| 2009-10-30 01:42:11 +0200 (Fri, 30 Oct 2009) \| 7 lines branches/zip: This test has been problematic for sometime now. The underlying bug is that the data dictionaries get out of sync. In the AUTOINC code we try and apply salve to the symptoms. In the past MySQL made some unrelated change and the dictionaries stopped getting out of sync and this test started to fail. Now, it seems they have reverted that changed and the test is passing again. I suspect this is not he last time that this test will change. r6124 \| jyang \| 2009-10-30 10:02:31 +0200 (Fri, 30 Oct 2009) \| 5 lines branches/zip: Correct the bug number for -r6109 change from # 48273 to #48237	16 years ago
Sergey Vojtovich	676bf0b30a	Applying InnoDB plugin snashot Detailed revision comments: r6114 \| vasil \| 2009-10-29 18:43:51 +0200 (Thu, 29 Oct 2009) \| 6 lines branches/zip: * Add ChangeLog entries for latest changes * Obey alphabetical order in the list of the files * White-space fixup	16 years ago
Sergey Vojtovich	976696fe4f	Applying InnoDB plugin snashot Detailed revision comments: r6113 \| vasil \| 2009-10-29 18:15:50 +0200 (Thu, 29 Oct 2009) \| 93 lines branches/zip: Merge r5912:6112 from branches/5.1: (after this merge the innodb-autoinc test starts to fail, but I commit anyway because it would be easier to investigate the failure this way) ------------------------------------------------------------------------ r5952 \| calvin \| 2009-09-22 19:45:07 +0300 (Tue, 22 Sep 2009) \| 7 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc branches/5.1: fix bug#42383: Can't create table 'test.bug39438' For embedded server, MySQL may pass in full path, which is currently disallowed. It is needed to relax the condition by accepting full paths in the embedded case. Approved by: Heikki (on IM) ------------------------------------------------------------------------ r6032 \| vasil \| 2009-10-01 15:55:49 +0300 (Thu, 01 Oct 2009) \| 8 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc branches/5.1: Fix Bug#38996 Race condition in ANALYZE TABLE by serializing ANALYZE TABLE inside InnoDB. Approved by: Heikki (rb://175) ------------------------------------------------------------------------ r6045 \| jyang \| 2009-10-08 02:27:08 +0300 (Thu, 08 Oct 2009) \| 7 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc A /branches/5.1/mysql-test/innodb_bug47777.result A /branches/5.1/mysql-test/innodb_bug47777.test branches/5.1: Fix bug #47777. Treat the Geometry data same as Binary BLOB in ha_innobase::store_key_val_for_row(), since the Geometry data is stored as Binary BLOB in Innodb. Review: rb://180 approved by Marko Makela. ------------------------------------------------------------------------ r6051 \| sunny \| 2009-10-12 07:05:00 +0300 (Mon, 12 Oct 2009) \| 6 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc M /branches/5.1/mysql-test/innodb-autoinc.result M /branches/5.1/mysql-test/innodb-autoinc.test branches/5.1: Ignore negative values supplied by the user when calculating the next value to store in dict_table_t. Setting autoincrement columns top negative values is undefined behavior and this change should bring the behavior of InnoDB closer to what users expect. Added several tests to check. rb://162 ------------------------------------------------------------------------ r6052 \| sunny \| 2009-10-12 07:09:56 +0300 (Mon, 12 Oct 2009) \| 4 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc M /branches/5.1/mysql-test/innodb-autoinc.result M /branches/5.1/mysql-test/innodb-autoinc.test branches/5.1: Reset the statement level autoinc counter on ROLLBACK. Fix the test results too. rb://164 ------------------------------------------------------------------------ r6053 \| sunny \| 2009-10-12 07:37:49 +0300 (Mon, 12 Oct 2009) \| 6 lines Changed paths: M /branches/5.1/handler/ha_innodb.cc M /branches/5.1/mysql-test/innodb-autoinc.result M /branches/5.1/mysql-test/innodb-autoinc.test branches/5.1: Copy the maximum AUTOINC value from the old table to the new table when MySQL does a CREATE INDEX ON T. This is required because MySQL does a table copy, rename and drops the old table. Fix Bug#47125: auto_increment start value is ignored if an index is created and engine=innodb rb://168 ------------------------------------------------------------------------ r6076 \| vasil \| 2009-10-14 19:30:12 +0300 (Wed, 14 Oct 2009) \| 4 lines Changed paths: M /branches/5.1/row/row0mysql.c branches/5.1: Fix typo. ------------------------------------------------------------------------	16 years ago
Sergey Vojtovich	b58b72f6ae	Applying InnoDB plugin snashot Detailed revision comments: r6112 \| calvin \| 2009-10-29 16:21:15 +0200 (Thu, 29 Oct 2009) \| 4 lines branches/zip: consideration for icc compilers Proposed by MySQL, and approved by Marko.	16 years ago
Sergey Vojtovich	640f10091f	Applying InnoDB plugin snashot Detailed revision comments: r6110 \| marko \| 2009-10-29 12:44:57 +0200 (Thu, 29 Oct 2009) \| 2 lines branches/zip: Makefile.am (INCLUDES): Merge a change from MySQL: Use $(srcdir)/include instead of $(top_srcdir)/storage/innobase/include. r6111 \| marko \| 2009-10-29 13:04:11 +0200 (Thu, 29 Oct 2009) \| 33 lines branches/zip: Fix corruption of buf_pool->LRU_old and improve debug assertions. This was reported as Issue #381. buf_page_set_old(): Assert that blocks may only be set old if buf_pool->LRU_old is initialized and buf_pool->LRU_old_len is nonzero. Assert that buf_pool->LRU_old points to the block at the old/new boundary. buf_LRU_old_adjust_len(): Invoke buf_page_set_old() after adjusting buf_pool->LRU_old and buf_pool->LRU_old_len, in order not to violate the added assertions. buf_LRU_old_init(): Replace buf_page_set_old() with a direct assignment to bpage->old, because these loops that initialize all the blocks would temporarily violate the assertions about buf_pool->LRU_old. buf_LRU_remove_block(): When setting buf_pool->LRU_old = NULL, also clear all bpage->old flags and set buf_pool->LRU_old_len = 0. buf_LRU_add_block_to_end_low(), buf_LRU_add_block_low(): Move the buf_page_set_old() call later in order not to violate the debug assertions. If buf_pool->LRU_old is NULL, set old=FALSE. buf_LRU_free_block(): Replace the UNIV_LRU_DEBUG assertion with a dummy buf_page_set_old() call that performs more thorough checks. buf_LRU_validate(): Do not tolerate garbage in buf_pool->LRU_old_len even if buf_pool->LRU_old is NULL. Check that bpage->old is monotonic. buf_relocate(): Make the UNIV_LRU_DEBUG checks stricter. buf0buf.h: Revise the documentation of buf_page_t::old and buf_pool_t::LRU_old_len.	16 years ago
Sergey Vojtovich	5b62cd212e	Applying InnoDB plugin snashot Detailed revision comments: r6109 \| jyang \| 2009-10-29 10:37:32 +0200 (Thu, 29 Oct 2009) \| 7 lines branches/zip: In os_mem_alloc_large(), if we fail to attach the shared memory, reset memory pointer ptr to NULL, and allocate memory from conventional pool. Bug #48237 Error handling in os_mem_alloc_large appears to be incorrect rb://198 Approved by: Marko	16 years ago
Sergey Vojtovich	be3fd511c5	Applying InnoDB plugin snashot Detailed revision comments: r6108 \| calvin \| 2009-10-29 07:58:04 +0200 (Thu, 29 Oct 2009) \| 5 lines branches/zip: close file handle when building with UNIV_HOTBACKUP The change does not affect regular InnoDB engine. Confirmed by Marko.	16 years ago
Sergey Vojtovich	d927bc67dc	Applying InnoDB plugin snashot Detailed revision comments: r6107 \| marko \| 2009-10-28 16:10:34 +0200 (Wed, 28 Oct 2009) \| 5 lines branches/zip: buf_page_set_old(): Improve UNIV_LRU_DEBUG diagnostics in order to catch the buf_pool->LRU_old corruption reported in Issue #381. buf_LRU_old_init(): Set the property from the tail towards the front of the buf_pool->LRU list, in order not to trip the debug check.	16 years ago
Sergey Vojtovich	74d505db0b	Applying InnoDB plugin snashot Detailed revision comments: r6105 \| calvin \| 2009-10-28 00:05:52 +0200 (Wed, 28 Oct 2009) \| 6 lines branches/zip: backport r3848 from 6.0 branch ---- branches/6.0: innobase_start_or_create_for_mysql(): Make the 10 MB minimum tablespace limit independent of UNIV_PAGE_SIZE. (Bug #41490)	16 years ago
Sergey Vojtovich	57b74a02fe	Applying InnoDB plugin snashot Detailed revision comments: r6103 \| marko \| 2009-10-26 15:46:18 +0200 (Mon, 26 Oct 2009) \| 4 lines branches/zip: row_ins_alloc_sys_fields(): Zero out the system columns DB_TRX_ID, DB_ROLL_PTR and DB_ROW_ID, in order to avoid harmless Valgrind warnings about uninitialized data. (The warnings were harmless, because the fields would be initialized at a later stage.)	16 years ago
Sergey Vojtovich	45846ff034	Applying InnoDB plugin snashot Detailed revision comments: r6102 \| marko \| 2009-10-26 09:32:23 +0200 (Mon, 26 Oct 2009) \| 1 line branches/zip: row_prebuilt_struct::prebuilts: Unused field, remove.	16 years ago
Sergey Vojtovich	e4a0641f13	Applying InnoDB plugin snashot Detailed revision comments: r6101 \| jyang \| 2009-10-23 11:45:50 +0300 (Fri, 23 Oct 2009) \| 7 lines branches/zip: Update test result with the WARN_LEVEL_ERROR to WARN_LEVEL_WARN change. This is the same result as submitted in rb://172 review, which approved by Sunny Bains and Marko.	16 years ago
Sergey Vojtovich	7d263d1072	Applying InnoDB plugin snashot Detailed revision comments: r6100 \| jyang \| 2009-10-22 06:51:07 +0300 (Thu, 22 Oct 2009) \| 6 lines branches/zip: As a request from mysql, WARN_LEVEL_ERROR cannot be used for push_warning_* call any more. Switch to WARN_LEVEL_WARN. Bug #47233. rb://172 approved by Sunny Bains and Marko.	16 years ago
unknown	9519c8e597	Manual Merge	16 years ago
Sergey Vojtovich	1e09890375	Applying InnoDB plugin snashot Detailed revision comments: r6099 \| jyang \| 2009-10-22 05:58:39 +0300 (Thu, 22 Oct 2009) \| 7 lines branches/zip: Port bug #46000 related changes from 5.1 to zip branch. Due to different code path for creating index in zip branch comparing to 5.1), the index reserved name check function is extended to be used in ha_innobase::add_index(). rb://190 Approved by: Marko	16 years ago
Sergey Vojtovich	73f883ff9b	Applying InnoDB plugin snashot Detailed revision comments: r6096 \| vasil \| 2009-10-19 16:06:09 +0300 (Mon, 19 Oct 2009) \| 4 lines branches/zip: Add ChangeLog entry for r6095.	16 years ago
Sergey Vojtovich	ad75bfc829	Applying InnoDB plugin snashot Detailed revision comments: r6095 \| vasil \| 2009-10-19 16:04:59 +0300 (Mon, 19 Oct 2009) \| 7 lines branches/zip: Fix Bug#47808 innodb_information_schema.test fails when run under valgrind by using the wait_until_rows_count macro that loops until the number of rows becomes 14 instead of sleep 0.1, which is obviously very fragile.	16 years ago
Sergey Vojtovich	53c8a0790e	Applying InnoDB plugin snashot Detailed revision comments: r6084 \| vasil \| 2009-10-15 08:21:17 +0300 (Thu, 15 Oct 2009) \| 4 lines branches/zip: Add ChangeLog entry for r6080.	16 years ago
Sergey Vojtovich	8b8fc30c52	Applying InnoDB plugin snashot Detailed revision comments: r6080 \| sunny \| 2009-10-15 01:29:01 +0300 (Thu, 15 Oct 2009) \| 3 lines branches/zip: Change page_mem_alloc_free() to inline. Fix Bug #47058 - Failure to compile innodb_plugin on solaris 10u7 + spro cc/CC 5.10	16 years ago
Sergey Vojtovich	8494bb83d9	Applying InnoDB plugin snashot Detailed revision comments: r6064 \| calvin \| 2009-10-13 18:23:35 +0300 (Tue, 13 Oct 2009) \| 4 lines branches/zip: non-functional changes Changes from MySQL to fix build issue. r6065 \| inaam \| 2009-10-13 20:43:13 +0300 (Tue, 13 Oct 2009) \| 7 lines branches/zip rb://182 Call fsync() on datafiles after a batch of pages is written to disk even when skip_innodb_doublewrite is set. Approved by: Heikki	16 years ago
Sergey Vojtovich	10456f81c2	Applying InnoDB plugin snapshot Detailed revision comments: r6049 \| vasil \| 2009-10-09 19:05:26 +0300 (Fri, 09 Oct 2009) \| 7 lines branches/zip: Fix compilation warning in Hot Backup: innodb/fil/fil0fil.c: In function 'fil_load_single_table_tablespace': innodb/fil/fil0fil.c:3253: warning: format '%lld' expects type 'long long int', but argument 6 has type 'ib_int64_t'	16 years ago
Sergey Vojtovich	9cdf2ea1ff	Applying InnoDB plugin snashot Detailed revision comments: r6048 \| vasil \| 2009-10-09 08:42:55 +0300 (Fri, 09 Oct 2009) \| 16 lines branches/zip: When scanning a directory readdir() is called and stat() after it, if a file is deleted between the two calls stat will fail and the whole precedure will fail. Change this behavior to continue with the next entry if stat() fails because of nonexistent file. This is transparent change as it will make it look as if the file was deleted before the readdir() call. This change is needed in order to fix https://svn.innodb.com/mantis/view.php?id=174 in which we need to abort if os_file_readdir_next_file() encounters "real" errors. Approved by: Marko, Pekka (rb://177)	16 years ago
Sergey Vojtovich	bcb97ed6d3	Applying InnoDB plugin snashot Detailed revision comments: r6046 \| pekka \| 2009-10-08 12:24:56 +0300 (Thu, 08 Oct 2009) \| 3 lines branches/zip: Revert r6044 which added os_file_is_same() function (issue#186). This functionality is moved to Hot Backup source tree.	16 years ago
Sergey Vojtovich	41ebf9751f	Applying InnoDB plugin snashot Detailed revision comments: r6044 \| pekka \| 2009-10-06 17:44:54 +0300 (Tue, 06 Oct 2009) \| 5 lines branches/zip: Add os_file_is_same() function for Hot Backup (inside ifdef UNIV_HOTBACKUP). This is part of the fix for Issue #186. Note! The Windows implementation is incomplete.	16 years ago
unknown	9819885177	BUG#48216 Replication fails on all slaves after upgrade to 5.0.86 on master When a sessione is closed, all temporary tables of the session are automatically dropped and are binlogged. But it will be binlogged with wrong database names when the length of the temporary tables' database names are greater than the length of the current database name or the current database is not set. Query_log_event's db_len is forgot to set when Query_log_event's db is set. This patch wrote code to set db_len immediately after db has set.	16 years ago
Sergey Vojtovich	b703edd747	Clean-ups after applying InnoDB snapshot 5.1-ss6129: - disabled main.innodb_bug47777.test with InnoDB plugin until fix for plugin is applied. - disabled main.innodb-autoinc.test (failing) - re-enabled main.innodb_bug39438.test - added error message suppression to innodb_bug39438, as requested by InnoDB/Oracle - reverted change to main.innodb_bug34300 as plugin specific.	16 years ago
Davi Arnaut	e077bb49d7	Bug#44952: Ndbd file system inconsistency error Backport a ndb patch: fix bug with crash during restart, where a mbyte incorrectly could be skipped, leading to "end of log wo/ finding gci".	16 years ago
Sergey Vojtovich	63ef110355	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6129 \| vasil \| 2009-10-30 17:14:22 +0200 (Fri, 30 Oct 2009) \| 4 lines branches/5.1: Revert a change to Makefile.am that sneaked unnoticed in c6127.	16 years ago
Sergey Vojtovich	66fc82247d	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6127 \| vasil \| 2009-10-30 11:18:25 +0200 (Fri, 30 Oct 2009) \| 18 lines branches/5.1: Backport c6121 from branches/zip: ------------------------------------------------------------------------ r6121 \| sunny \| 2009-10-30 01:42:11 +0200 (Fri, 30 Oct 2009) \| 7 lines Changed paths: M /branches/zip/mysql-test/innodb-autoinc.result branches/zip: This test has been problematic for sometime now. The underlying bug is that the data dictionaries get out of sync. In the AUTOINC code we try and apply salve to the symptoms. In the past MySQL made some unrelated change and the dictionaries stopped getting out of sync and this test started to fail. Now, it seems they have reverted that changed and the test is passing again. I suspect this is not he last time that this test will change. ------------------------------------------------------------------------	16 years ago
Sergey Vojtovich	37d83e4d48	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6125 \| vasil \| 2009-10-30 10:31:23 +0200 (Fri, 30 Oct 2009) \| 4 lines branches/5.1: White-space fixup.	16 years ago
Sergey Vojtovich	f276d54404	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6123 \| jyang \| 2009-10-30 05:43:06 +0200 (Fri, 30 Oct 2009) \| 8 lines branches/5.1: In os_mem_alloc_large(), if we fail to attach the shared memory, reset memory pointer ptr to NULL, and allocate memory from conventional pool. This is a port from branches/zip. Bug #48237 Error handling in os_mem_alloc_large appears to be incorrect rb://198 Approved by: Marko	16 years ago
Sergey Vojtovich	c29b740bec	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6122 \| jyang \| 2009-10-30 05:18:38 +0200 (Fri, 30 Oct 2009) \| 7 lines branches/5.1: Chnage WARN_LEVEL_ERROR to WARN_LEVEL_WARN for push_warning_printf() call in innodb. Fix Bug#47233: Innodb calls push_warning(MYSQL_ERROR::WARN_LEVEL_ERROR) rb://170 approved by Marko.	16 years ago
Sergey Vojtovich	3af62819dc	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6076 \| vasil \| 2009-10-14 19:30:12 +0300 (Wed, 14 Oct 2009) \| 4 lines branches/5.1: Fix typo.	16 years ago
Sergey Vojtovich	ebc3626738	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6052 \| sunny \| 2009-10-12 07:09:56 +0300 (Mon, 12 Oct 2009) \| 4 lines branches/5.1: Reset the statement level autoinc counter on ROLLBACK. Fix the test results too. rb://164 r6053 \| sunny \| 2009-10-12 07:37:49 +0300 (Mon, 12 Oct 2009) \| 6 lines branches/5.1: Copy the maximum AUTOINC value from the old table to the new table when MySQL does a CREATE INDEX ON T. This is required because MySQL does a table copy, rename and drops the old table. Fix Bug#47125: auto_increment start value is ignored if an index is created and engine=innodb rb://168	16 years ago
Sergey Vojtovich	c8d97af6b0	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6051 \| sunny \| 2009-10-12 07:05:00 +0300 (Mon, 12 Oct 2009) \| 6 lines branches/5.1: Ignore negative values supplied by the user when calculating the next value to store in dict_table_t. Setting autoincrement columns top negative values is undefined behavior and this change should bring the behavior of InnoDB closer to what users expect. Added several tests to check. rb://162	16 years ago
Sergey Vojtovich	71d24a2371	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6045 \| jyang \| 2009-10-08 02:27:08 +0300 (Thu, 08 Oct 2009) \| 7 lines branches/5.1: Fix bug #47777. Treat the Geometry data same as Binary BLOB in ha_innobase::store_key_val_for_row(), since the Geometry data is stored as Binary BLOB in Innodb. Review: rb://180 approved by Marko Makela.	16 years ago
Sergey Vojtovich	7e317016e6	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r6032 \| vasil \| 2009-10-01 15:55:49 +0300 (Thu, 01 Oct 2009) \| 8 lines branches/5.1: Fix Bug#38996 Race condition in ANALYZE TABLE by serializing ANALYZE TABLE inside InnoDB. Approved by: Heikki (rb://175)	16 years ago
Sergey Vojtovich	e7452e7b68	Applying InnoDB snashot 5.1-ss6129 Detailed revision comments: r5952 \| calvin \| 2009-09-22 19:45:07 +0300 (Tue, 22 Sep 2009) \| 7 lines branches/5.1: fix bug#42383: Can't create table 'test.bug39438' For embedded server, MySQL may pass in full path, which is currently disallowed. It is needed to relax the condition by accepting full paths in the embedded case. Approved by: Heikki (on IM)	16 years ago
Martin Hansson	740b7c4e36	Bug#47925: regression of range optimizer and date comparison in 5.1.39! When a query was using a DATE or DATETIME value formatted using any other separator characters beside hyphen '-', a query with a greater-or-equal '>=' condition matching only the greatest value in an indexed column, the result was empty if index range scan was employed. The range optimizer got a new feature between 5.1.38 and 5.1.39 that changes a greater-or-equal condition to a greater-than if the value matching that in the query was not present in the table. But the value comparison function compared the dates as strings instead of dates. The bug was fixed by splitting the function get_date_from_str in two: One part that parses and does error checking. This function is now visible outside the module. The old get_date_from_str now calls the new function. mysql-test/r/range.result: Bug#47925: Test result mysql-test/t/range.test: Bug#47925: Test case sql/item.cc: Bug#47925: Fix + some edit on the comments sql/item.h: Bug#47925: Changed function signature sql/item_cmpfunc.cc: Bug#47925: Split function in two sql/item_cmpfunc.h: Bug#47925: Declaration of new function sql/opt_range.cc: Bug#47925: Added THD to function call sql/time.cc: Bug#47925: Added microsecond comparison	16 years ago
Davi Arnaut	1955c86624	Automerge.	16 years ago
Davi Arnaut	1ca80ed19e	Bug#48370: Absolutely wrong calculations with GROUP BY and decimal fields when using IF Bug#45261: Crash, stored procedure + decimal Revert fix for Bug#45261 due to unforeseen bugs.	16 years ago
Sergey Vojtovich	cd167ee2e9	Merge innodb-5.1-ss6129 to mysql-5.1-bugteam.	16 years ago
Vladislav Vaintroub	b51777484f	merge	16 years ago
Vladislav Vaintroub	2377eed362	Bug #47423 mtr connects to wrong database The reason for the bug is that mysqtest as well as other client tools running in test suite (mysqlbinlog, mysqldump) will first try to connect whatever database has created shared memory with default base name "MySQL" and use this. (Same effect could be seen on Unix if mtr would not care to calculate "port" and "socket" parameter). The fix ensures that all client tools and running in mtr use unique per-database shared memory base parameters, so there is no possibility to clash with already installed one. We use socket name for shared memory base (it's known to be unique). This shared-memory-base is written to the MTR config file to the [client] and [mysqld] sections. Fix made also made sure all client tools understand and correctly handle --shared-memory-base. Prior to this patch it was not the case for mysqltest, mysqlbinlog and mysql_client_test. All new connections done from mtr scripts via connect() will by default set shared-memory-base. And finally, there is a possibility to force shared memory or pipe connection and overwrite shared memory/pipe base name from within mtr scripts via optional PIPE or SHM modifier. This functionality was manually backported from 6.0 (original patch http://lists.mysql.com/commits/74749)	16 years ago
Vladislav Vaintroub	e080080711	Bug#47571: idle named pipe connection is unkillable Bug#31621: Windows server hanging during shutdown using named pipes and idle connection Problem: when idle pipe connection is forcefully closed with KILL statement or when the server goes down, thread that is closing connection would hang infinitely in CloseHandle(). The reason for the hang is that named pipe operations are performed synchronously. In this mode all IOs on pipe are serialized, that is CloseHandle() will not abort ReadFile() in another thread, but wait for ReadFile() to complete. The fix implements asynchrnous mode for named pipes, where operation of file are not synchronized. Read/Write operation would fire an async IO and wait for either IO completion or timeout. Note, that with this patch timeouts are properly handled for named pipes. Post-review: Win32 timeout code has been fixed for named pipes and shared memory. We do not store pointer to NET in vio structure, only the read and write timeouts. include/violite.h: Add pipe_overlapped to Vio structure for async IO for named pipes. sql-common/client.c: Use asynchronous pipe IO. sql/mysqld.cc: Use asynchronous pipe IO. vio/vio.c: -Refactor timeouts for win32 protocols: shared memory and named pipes. Store read/write timeout in VIO structure, instead of storing pointer to NET. New function vio_win32_timeout called indirectly via vio_timeout changes these values. vio/vio_priv.h: Remove vio_ignore_timeout. Add vio_win32_timeout to be used for named pipes and shared memory. vio/viosocket.c: Use async IO for named pipes. After issuing IO, wait for either IO completion, pipe_close_event or timeout. Refactor timeouts for named pipe and shared memory.	16 years ago
Davi Arnaut	d87301d7d9	Automerge.	16 years ago

1 2 3 4 5 ...

58588 Commits (0212e736136432f8d0442703b55220c0bd9c505e) All Branches Search

58588 Commits (0212e736136432f8d0442703b55220c0bd9c505e)

All Branches