- 29 Jul, 2010 2 commits
-
-
Vasil Dimov authored
-
Vasil Dimov authored
-
- 28 Jul, 2010 3 commits
-
-
Gleb Shchepa authored
DELETE statement Single-table delete ordered by a field that has a hash-type index may cause an assertion failure or a crash. An optimization added by the fix for the bug 36569 forced the optimizer to use ORDER BY-compatible indices when applicable. However, the existence of unsorted indices (HASH index algorithm for some engines such as MEMORY/HEAP, NDB) was ignored. The test_if_order_by_key function has been modified to skip unsorted indices. mysql-test/r/heap_hash.result: Test case for bug #55472. mysql-test/t/heap_hash.test: Test case for bug #55472. sql/sql_select.cc: Bug #55472: Assertion failed in heap_rfirst function of hp_rfirst.c on DELETE statement The test_if_order_by_key function has been modified to skip unsorted indices.
-
Vasil Dimov authored
-
Vasil Dimov authored
-
- 26 Jul, 2010 1 commit
-
-
Davi Arnaut authored
The problem was that the optimize method of the ARCHIVE storage engine was not preserving the FRM embedded in the ARZ file when rewriting the ARZ file for optimization. The ARCHIVE engine stores the FRM in the ARZ file so it can be transferred from machine to machine without also copying the FRM -- the engine restores the embedded FRM during discovery. The solution is to copy over the FRM when rewriting the ARZ file. In addition, some initial error checking is performed to ensure garbage is not copied over. mysql-test/t/archive.test: Add test case for Bug#45377. storage/archive/azio.c: Add error checking to ensure that the I/O operations are successful. storage/archive/ha_archive.cc: Copy over the embedded FRM.
-
- 28 Jul, 2010 1 commit
-
-
Luis Soares authored
-
- 27 Jul, 2010 1 commit
-
-
Davi Arnaut authored
Workaround a interface problem with the atomic macros that was causing warnings. The correct type is retrieved using typeof if compiling with GCC.
-
- 26 Jul, 2010 5 commits
-
-
Davi Arnaut authored
Remove ASM for MC68000 and Vax.
-
Davi Arnaut authored
Remove 32-bit SPARC specific code.
-
Matthias Leich authored
into actual tree. No conflicts.
-
Jimmy Yang authored
rb://408 approved by Sunny Bains
-
Alexander Nozdrin authored
-
- 25 Jul, 2010 1 commit
-
-
Vladislav Vaintroub authored
* Fixed obvious errors (HAVE_BROKEN_PREAD is not true for on any of systems we use, definitely not on HPUX) * Remove other junk flags for OSX and HPUX * Avoid checking type sizes in universal builds on OSX, again (CMake2.8.0 fails is different architectures return different results) * Do not compile template instantiation stuff unless EXPLICIT_TEMPLATE_INSTANTIATION is used. * Some cleanup (make gen_lex_hash simpler, avoid dependencies) * Exclude some unused files from compilation (strtol.c etc)
-
- 24 Jul, 2010 4 commits
-
-
Vladislav Vaintroub authored
Fix some issues with WiX packaging, particularly major upgrade and change scenarios. * remember binary location and data location (for major upgrade) * use custom UI, which is WiX Mondo extended for major upgrade dialog (no feature selection screen shown on major upgrade, only upgrade confirmation). This is necessary to prevent changing installation path during upgrade (services are not reregistered, so they would have invalid binary path is it is changed) * Hide datafiles that are installed into ProgramFiles, show ones that are installed in ProgramData * Make MSI buildable with nmake * Fix autotools "make dist" Makefile.am: Fix autotools "make dist" configure.in: Fix autotools "make dist" packaging/Makefile.am: Fix autotools "make dist" packaging/WiX/CMakeLists.txt: Use custom UI, for major upgrades packaging/WiX/CPackWixConfig.cmake: Show user editable datafiles in feature selection dialog, not datafiles installed into ProgramFiles directory packaging/WiX/create_msi.cmake.in: Use custom UI, fix nmake build for installer packaging/WiX/custom_ui.wxs: Use custom UI packaging/WiX/extra.wxs.in: Show user editable datafiles in feature selection dialog, not datafiles installed into ProgramFiles directory packaging/WiX/mysql_server.wxs.in: Remember install locations of binaries and user editable datafiles.
-
Davi Arnaut authored
Fix assorted warnings in order for the warning-mode to be effective.
-
Davi Arnaut authored
-
Davi Arnaut authored
Post-merge fix: remove remaining casts which are now unnecessary and are actually causing warnings.
-
- 23 Jul, 2010 11 commits
-
-
Davi Arnaut authored
Remove wrappers around inline -- static inline is used without wrappers throughout the source code. We rely on the compiler or linker to eliminate unused static functions.
-
Davi Arnaut authored
Remove workarounds for ancient systems. mysys/default.c: Make cast more explicit to ensure a correct offset.
-
Davi Arnaut authored
Remove unused string functions. include/m_string.h: Remove prototypes for unused string functions and for functions that do not exist anymore.
-
Davi Arnaut authored
Remove unused macros or macro which are always defined. include/my_global.h: Remove unused macros and move macros which aren't used globally.
-
Davi Arnaut authored
Remove the obsolete and buggy bmove512, use memcpy instead.
-
Davi Arnaut authored
Remove the ancient and dead raid code. By now, even the server side has been removed.
-
Davi Arnaut authored
Remove unused source code and associated paraphernalia.
-
Davi Arnaut authored
Remove Windows related files which aren't used anymore.
-
Davi Arnaut authored
Remove unused variables.
-
Davi Arnaut authored
Remove code that has been disabled for a long time.
-
Vasil Dimov authored
A change in the default values of some config parameters caused this test to fail, adjust the test and make it more robust so it does not fail for the same reason in the future.
-
- 22 Jul, 2010 3 commits
-
-
Luis Soares authored
sporadically There are two problems: 1. When closing temporary tables, during the THD clean up - and after the session connection was already closed, there is a chance we can push an error into the THD diagnostics area, if the writing of the implicit DROP event to the binary log fails for some reason. As a consequence an assertion can be triggered, because at that point the diagnostics area is already set. 2. Using push_warning with MYSQL_ERROR::WARN_LEVEL_ERROR is a bug. Given that close_temporary_tables is mostly called from THD::cleanup - ie, with the session already closed, we fix problem #1 by allowing the diagnostics area to be overwritten. There is one other place in the code that calls close_temporary_tables - while applying Start_log_event_v3. To cover that case, we make close_temporary_tables to return the error, thus, propagating upwards in the stack. To fix problem #2, we replace push_warning with sql_print_error. sql/log_event.cc: Added handling of error returned by close_temporary_tables to Start_log_event_v3::do_apply_event. sql/sql_base.cc: Three changes to close_temporary_tables: 1. it returns a boolean now (instead of void) 2. it uses sql_print_error instead of push_warning when writing to binary log fails 3. we set can_overwrite_status before writing to the binary log, thence not risking triggering an assertion by any other push into diagnostics area happening inside mysql_bin_log.write. sql/sql_base.h: Changed the interface of close_temporary_tables so that it returns bool instead of void.
-
Vasil Dimov authored
-
Sunny Bains authored
release a dirty page in the middle of a mini-transaction. Replace the code with an assertion that checks for this condition. Original svn revision was: r6330.
-
- 21 Jul, 2010 4 commits
-
-
Sunny Bains authored
Silence the UNIV_SYNC_DEBUG assertion failure while upgrading old data files to multiple rollback segments during server startup. Because the upgrade takes place while InnoDB is running a single thread, we can safely ignore the latching order checks without fearing deadlocks. innobase_start_or_create_for_mysql(): Set srv_is_being_started = FALSE only after trx_sys_create_rsegs() has completed. sync_thread_add_level(): If srv_is_being_started, ignore latching order violations for SYNC_TRX_SYS_HEADER and SYNC_IBUF_BITMAP. Create all the non-IO threads after creating the extra rollback segments. Patch originally from Marko with some additions by Sunny.
-
Sunny Bains authored
Get rid of at least on suspicious path. Ensure that the purge thread doesn't acquire a mutex after it has signalled shutdown.
-
Vasil Dimov authored
InnoDB 1.1.1 was released with MySQL 5.5.5-m3
-
Vasil Dimov authored
(resolving conflicts in mysql-test/suite/rpl/t/rpl_sync-slave.opt and configure.cmake)
-
- 20 Jul, 2010 3 commits
-
-
Calvin Sun authored
This patch was originally developed by Vladislav Vaintroub. The main changes are: * Use TryEnterCriticalSection in os_fast_mutex_trylock(). * Use lightweight condition variables on Vista or later Windows; but fall back to events on older Windows, such as XP. This patch also fixes the following bugs: bug# 52102 InnoDB Plugin shows performance drop compared to InnoDB on Windows bug# 53204 os_fastmutex_trylock is implemented incorrectly on Windows rb://363 approved by Inaam Rana
-
Matthias Leich authored
The reason for the bug above is unclear but - Modify pfs_upgrade so that it's result is easier to analyze in case something fails - Fix several minor weaknesses which could cause that a successing test (either an already existing or a to be developed one) fails because of imperfect cleanup, too slow disconnected sessions etc. should either fix the bug or reduce it's probability or at least make the analysis of failures easier. mysql-test/suite/perfschema/include/upgrade_check.inc: New include file which contains redundant stuff taken from pfs_upgrade.test. Remove any file which might harm analysis of suspicious results. mysql-test/suite/perfschema/r/query_cache.result: Updated results mysql-test/suite/perfschema/r/selects.result: Updated results mysql-test/suite/perfschema/t/bad_option_1.test: Add the missing remove_file at beginning and end of test. mysql-test/suite/perfschema/t/bad_option_2.test: Add the missing remove_file at beginning and end of test. mysql-test/suite/perfschema/t/global_read_lock.test: Add a wait routine which ensures that the disconnect is really completed when the test ends. mysql-test/suite/perfschema/t/pfs_upgrade.test: - Move redundant actions to include/upgrade_check.inc - Add preemptive removal of files mysql-test/suite/perfschema/t/privilege.test: Add a wait routine which ensures that the disconnect is really completed when the test ends. mysql-test/suite/perfschema/t/query_cache.test: Add "flush status" so that counters are reset. (./mtr --repeat=2 perfschema.query_cache failed) mysql-test/suite/perfschema/t/read_only.test: Add a wait routine which ensures that the disconnect is really completed when the test ends. mysql-test/suite/perfschema/t/selects-master.opt: Needed for running with enabled event-scheduler mysql-test/suite/perfschema/t/selects.test: - Correct the sub test for the EVENT scheduler - Replace "sleep" by wait_routine - Add premptive cleanups like "DROP ... IF EXISTS ..."
-
Davi Arnaut authored
-
- 23 Jul, 2010 1 commit
-
-
Davi Arnaut authored
Bug#52261: 64 bit atomic operations do not work on Solaris i386 gcc in debug compilation One of the various problems was that the source operand to CMPXCHG8b was marked as a input/output operand, causing GCC to use the EBX register as the destination register for the CMPXCHG8b instruction. This could lead to crashes as the EBX register is also implicitly used by the instruction, causing the value to be potentially garbaged and a protection fault once the value is used to access a position in memory. Another problem was the lack of proper clobbers for the atomic operations and, also, a discrepancy between the implementations for the Compare and Set operation. The specific problems are described and fixed by Kristian Nielsen patches: Patch: 1 Fix bugs in my_atomic_cas*(val,cmp,new) that *cmp is accessed after CAS succeds. In the gcc builtin implementation, problem was that *cmp was read again after atomic CAS to check if old *val == *cmp; this fails if CAS is successful and another thread modifies *cmp in-between. In the x86-gcc implementation, problem was that *cmp was set also in the case of successful CAS; this means there is a window where it can clobber a value written by another thread after successful CAS. Patch 2: Add a GCC asm "memory" clobber to primitives that imply a memory barrier. This signifies to GCC that any potentially aliased memory must be flushed before the operation, and re-read after the operation, so that read or modification in other threads of such memory values will work as intended. In effect, it makes these primitives work as memory barriers for the compiler as well as the CPU. This is better and more correct than adding "volatile" to variables. include/atomic/gcc_builtins.h: Do not read from *cmp after the operation as it might be already gone if the operation was successful. include/atomic/nolock.h: Prefer system provided atomics over the broken x86 asm. include/atomic/x86-gcc.h: Do not mark source operands as input/output operands. Add proper memory clobbers. include/my_atomic.h: Add notes about my_atomic_add and my_atomic_cas behaviors. unittest/mysys/my_atomic-t.c: Remove work around, if it fails, there is either a problem with the atomic operations code or the specific compiler version should be black-listed.
-