An error occurred fetching the project authors.
  1. 25 Jul, 2013 1 commit
  2. 04 Jul, 2013 1 commit
  3. 28 May, 2013 1 commit
    • unknown's avatar
      MDEV-4478: Implement GTID "strict mode" · 1d474979
      unknown authored
      When @@GLOBAL.gtid_strict_mode=1, then certain operations result
      in error that would otherwise result in out-of-order binlog files
      between servers.
      
      GTID sequence numbers are now allocated independently per domain;
      this results in less/no holes in GTID sequences, increasing the
      likelyhood that diverging binlogs will be caught by the slave when
      GTID strict mode is enabled.
      1d474979
  4. 10 May, 2013 1 commit
    • Michael Widenius's avatar
      Added some fixes that should make MyISAM & Aria REPAIR work with more than 4G records · e9a16310
      Michael Widenius authored
      - If one specifies --force twice to myisamchk and aria_chk, then we will try to finnish the repair even if sort_buffer would be too small.
        This was done by dynamically allocate buffer handler objects as long as memory lasts.
      - New option for myisamchk and aria_chk: create-missing-keys
      - Changed default size of myisam_sort_buffer_size from 8M to 128M.
      - Changed default size of sort_buffer_size in aria_chk from 128M to 256M.
      - Increased information in error message about 'sort_buffer_size' beeing to small.
      - Print also to 'show warnings' if repair was retried.
      - Increased size of internal sort-buffer-readers from 16K to 128K
      - Changed printing of 'number of records' to use %ll instead of casting to long
      - Changed buffer sizes for myisam and aria to use MY_ALIGN_DOWN() to get same number of bytes allocated on different machines.
      
      
      
      
      
      include/my_global.h:
        Added MY_ALIGN_DOWN() to get previous alignment (for big memory areas)
      include/myisam.h:
        Increased size of types to be able to handle more records
      include/myisamchk.h:
        Increased size of types to be able to handle more records
        Added T_FORCE_SORT_MEMORY to force repair to work even if sort_buffer would not be big enough
      mysql-test/r/myisam.result:
        Updated result
      mysql-test/r/mysqld--help.result:
        Updated result
      mysql-test/r/repair.result:
        Updated result
      mysql-test/suite/maria/maria.result:
        Added test cases for some fixed bugs in MyISAM to verify that Aria doesn't have them too.
      mysql-test/suite/maria/maria.test:
        Added test cases for some fixed bugs in MyISAM to verify that Aria doesn't have them too.
      mysql-test/suite/maria/maria3.result:
        Updated result after sort buffer size increase
      mysql-test/suite/sys_vars/r/aria_sort_buffer_size_basic.result:
        Updated result after sort buffer size increase
      mysql-test/suite/sys_vars/r/myisam_sort_buffer_size_basic.result:
        Updated result after sort buffer size increase
      mysql-test/suite/sys_vars/t/myisam_sort_buffer_size_basic.test:
        Updated result after sort buffer size increase
      mysql-test/t/myisam.test:
        Fixed error messages to not print system specific data
      mysql-test/t/repair.test:
        Fixed error messages to not print system specific data
      storage/maria/ha_maria.cc:
        Print also to 'show warnings' if repair was retried
        Changed default size of sort_buffer_size from 128M to 256M (same as in mysqld)
      storage/maria/ma_check.c:
        Renamed USE_BUFFER_INIT -> PAGE_BUFFER_INIT
      storage/maria/ma_sort.c:
        Increased size of internal sort-buffer-readers from 16K to 128K
        Increased size of types to be able to handle more records
        Added support for T_FORCE_SORT_MEMORY
        Don't allocate too many extra BUFFPEK at a time (they are probably not needed)
        Improved error message for "sort_buffer_size is too small"
        Changed printing of 'number of records' to use %ll instead of casting to long
        Fixed bug where maria_update_key_parts() was called too early.
        Fixed bug in detecting result from read_to_buffer().
        Added 'out of memory' checking when calling 'alloc_dynamic()'.
      storage/maria/maria_chk.c:
        Added --create-missing-keys
        If one specifies --force twice then we will try to finnish the repair even if sort_buffer would be too small.
        check_param.sort_buffer_length varialble was used with wrong type.
      storage/maria/maria_def.h:
        Increased size of types to be able to handle more records
        Use MY_ALIGN_DOWN() to get same number of bytes allocated on different machines
        Renamed USE_BUFFER_INIT -> PAGE_BUFFER_INIT
      storage/maria/maria_ftdump.c:
        Renamed USE_BUFFER_INIT -> PAGE_BUFFER_INIT
      storage/maria/maria_read_log.c:
        Use PAGE_BUFFER_INIT for page cache
      storage/myisam/ha_myisam.cc:
        Changed default size of myisam_sort_buffer_size from 8M to 128M
      storage/myisam/mi_check.c:
        Renamed USE_BUFFER_INIT -> KEY_BUFFER_INIT
      storage/myisam/myisam_ftdump.c:
        Renamed USE_BUFFER_INIT -> KEY_BUFFER_INIT
      storage/myisam/myisamchk.c:
        Added --create-missing-keys
        If one specifies --force twice then we will try to finnish the repair even if sort_buffer would be too small.
        check_param.sort_buffer_length varialble was used with wrong type.
        Renamed USE_BUFFER_INIT -> KEY_BUFFER_INIT
      storage/myisam/myisamdef.h:
        Increased SORT_BUFFER_INIT to 64M
        (speeds up repair a lot and most machines have nowadays a lot of memory)
        Use MY_ALIGN_DOWN() to get same number of bytes allocated on different machines
        Renamed USE_BUFFER_INIT -> KEY_BUFFER_INIT
      storage/myisam/sort.c:
        Increased size of internal sort-buffer-readers from 16K to 128K
        Increased size of types to be able to handle more records
        Added support for T_FORCE_SORT_MEMORY
        Don't allocate too many extra BUFFPEK at a time (they are probably not needed)
        Improved error message for "sort_buffer_size is too small"
        Changed printing of 'number of records' to use %ll instead of casting to long
        Fixed bug in detecting result from read_to_buffer().
        Added 'out of memory' checking when calling 'alloc_dynamic()'.
      e9a16310
  5. 20 Apr, 2013 1 commit
    • Alexander Barkov's avatar
      Fixing a few problems found by Build Bot after merging the CONNECT engine. · d97cd116
      Alexander Barkov authored
      modified:
        @ mysql-test/r/mysqld--help.result
        @ mysql-test/t/mysqld--help.test
        Supressing information about "--connect" in "mysqld --help" output,
        as it depends on the build parameters.
        As a side effect information about --connect-timeout is now also suppressed :(
      
        @ storage/connect/CMakeLists.txt
        Removing gcc warning switches that do not exists in some older gcc versions.
      
        @ storage/connect/ha_connect.cc
        Adding a quick fix: cast from "const char *" to "char *".
        Olivier should do a better fix eventually.
      d97cd116
  6. 18 Apr, 2013 1 commit
    • unknown's avatar
      MDEV-4345 · 906bcd98
      unknown authored
      Sampling of selectivity of LIKE predicate.
      906bcd98
  7. 10 Apr, 2013 1 commit
    • Sergei Golubchik's avatar
      portability fixes for mysql-test · 6675e769
      Sergei Golubchik authored
      mysql-test/r/mysqld--help.result:
        that's default to number of CPUs
      mysql-test/suite/archive/discover.test:
        move_file uses rename(2), which may end up
        with "Invalid cross-device link"
      mysql-test/suite/archive/partition_archive.test:
        on Solaris the error message is different
      6675e769
  8. 07 Apr, 2013 1 commit
  9. 31 Mar, 2013 1 commit
  10. 26 Mar, 2013 2 commits
    • unknown's avatar
      MDEV-26: Global transaction ID · 13173a2f
      unknown authored
      Adjust full test suite to work with GTID.
      
      Huge patch, mainly due to having to update .result file for all SHOW BINLOG
      EVENTS and mysqlbinlog outputs, where the new GTID events pop up.
      
      Everything was painstakingly checked to be still correct and valid .result
      file updates.
      13173a2f
    • Igor Babaev's avatar
      Added histogams for table columns. · b6018239
      Igor Babaev authored
      b6018239
  11. 11 Mar, 2013 1 commit
  12. 25 Feb, 2013 1 commit
  13. 15 Dec, 2012 1 commit
    • Sergei Golubchik's avatar
      MDEV-3860 backport --plugin-load-add (and related mysql-test changes) · fa7220c0
      Sergei Golubchik authored
        revno: 3383
        revision-id: georgi.kodinov@oracle.com-20110818083108-qa3h3ufqu4zne80a
        committer: Georgi Kodinov <Georgi.Kodinov@Oracle.com>
        timestamp: Thu 2011-08-18 11:31:08 +0300
        message:
      
        Bug #11766001: 59026: ALLOW MULTIPLE --PLUGIN-LOAD OPTIONS
        
        Implemented support for a new command line option :
        --plugin-load-add=<comma-separated-name-equals-value-list>
        This option takes the same type of arguments that --plugin-load does
        and complements --plugin-load (that continues to operate as before) by
        appending its argument to the list specified by --plugin-load.
        So --plugin-load can be considered a composite option consisting of 
        resetting the plugin load list and then calling --plugin-load-add to process
        the argument.
        Note that the order in which you specify --plugin-load and --plugin-load-add 
        is important : "--plugin-load=x --plugin-load-add=y" will be equivalent to
        "--plugin-load=x,y" whereas "--plugin-load-add=y --plugin-load=x" will be 
        equivalent to "plugin-load=x".
        
        Incompatible change : the --help --verbose command will no longer print the 
        --plugin-load variable's values (as it doesn't have one). Otherwise both --plugin-load 
        and --plugin-load-add are mentioned in it.
      fa7220c0
  14. 28 Sep, 2012 1 commit
  15. 08 Sep, 2012 1 commit
    • Michael Widenius's avatar
      Added new status variables: · 962dcca9
      Michael Widenius authored
      feature_dynamic_columns,feature_fulltext,feature_gis,feature_locale,feature_subquery,feature_timezone,feature_trigger,feature_xml
      Opened_views, Executed_triggers, Executed_events
      Added new process status 'updating status' as part of 'freeing items'
      
      mysql-test/r/features.result:
        Test of feature_xxx status variables
      mysql-test/r/mysqld--help.result:
        Removed duplicated 'language' variable.
      mysql-test/r/view.result:
        Test of opened_views
      mysql-test/suite/rpl/t/rpl_start_stop_slave.test:
        Write more information on failure
      mysql-test/t/features.test:
        Test of feature_xxx status variables
      mysql-test/t/view.test:
        Test of opened_views
      sql/event_scheduler.cc:
        Increment executed_events status variable
      sql/field.cc:
        Increment status variable
      sql/item_func.cc:
        Increment status variable
      sql/item_strfunc.cc:
        Increment status variable
      sql/item_subselect.cc:
        Increment status variable
      sql/item_xmlfunc.cc:
        Increment status variable
      sql/mysqld.cc:
        Add new status variables to 'show status'
      sql/mysqld.h:
        Added executed_events
      sql/sql_base.cc:
        Increment status variable
      sql/sql_class.h:
        Add new status variables
      sql/sql_parse.cc:
        Added new process status 'updating status' as part of 'freeing items'
      sql/sql_trigger.cc:
        Increment status variable
      sql/sys_vars.cc:
        Increment status variable
      sql/tztime.cc:
        Increment status variable
      962dcca9
  16. 22 Aug, 2012 1 commit
  17. 03 Jun, 2012 1 commit
    • Igor Babaev's avatar
      Removed the server option --stat-tables. · 96b1c602
      Igor Babaev authored
      Renamed the system variable optimizer_use_stat_tables to use_stat_tables.
      This variable now has only 3 possible values:
      'never', 'complementary', 'preferably'.
      If the server has been launched with
      --use-stat-tables='complementary'|'preferably'
      then the statictics tables can be employed by the optimizer and by the
      ANALYZE command. 
      96b1c602
  18. 17 May, 2012 1 commit
    • unknown's avatar
      Fix for bug lp:944706, task MDEV-193 · 6eab1302
      unknown authored
      The patch enables back constant subquery execution during
      query optimization after it was disabled during the development
      of MWL#89 (cost-based choice of IN-TO-EXISTS vs MATERIALIZATION).
      
      The main idea is that constant subqueries are allowed to be executed
      during optimization if their execution is not expensive.
      
      The approach is as follows:
      - Constant subqueries are recursively optimized in the beginning of
        JOIN::optimize of the outer query. This is done by the new method
        JOIN::optimize_constant_subqueries(). This is done so that the cost
        of executing these queries can be estimated.
      - Optimization of the outer query proceeds normally. During this phase
        the optimizer may request execution of non-expensive constant subqueries.
        Each place where the optimizer may potentially execute an expensive
        expression is guarded with the predicate Item::is_expensive().
      - The implementation of Item_subselect::is_expensive has been extended
        to use the number of examined rows (estimated by the optimizer) as a
        way to determine whether the subquery is expensive or not.
      - The new system variable "expensive_subquery_limit" controls how many
        examined rows are considered to be not expensive. The default is 100.
      
      In addition, multiple changes were needed to make this solution work
      in the light of the changes made by MWL#89. These changes were needed
      to fix various crashes and wrong results, and legacy bugs discovered
      during development.
      6eab1302
  19. 08 May, 2012 1 commit
  20. 23 Feb, 2012 1 commit
  21. 20 Feb, 2012 1 commit
  22. 18 Feb, 2012 1 commit
  23. 26 Jan, 2012 1 commit
  24. 25 Jan, 2012 1 commit
    • Dmitry Shulga's avatar
      Fixed bug#11753187 (formerly known as bug 44585): SP_CACHE BEHAVES AS · 076bf863
      Dmitry Shulga authored
      MEMORY LEAK.
      
      Background:
       - There are caches for stored functions and stored procedures (SP-cache);
       - There is no similar cache for events;
       - Triggers are cached together with TABLE objects;
       - Those SP-caches are per-session (i.e. specific to each session);
       - A stored routine is represented by a sp_head-instance internally;
       - SP-cache basically contains sp_head-objects of stored routines, which
         have been executed in a session;
       - sp_head-object is added into the SP-cache before the corresponding
         stored routine is executed;
       - SP-cache is flushed in the end of the session.
      
      The problem was that SP-cache might grow without any limit. Although this
      was not a pure memory leak (the SP-cache is flushed when session is closed),
      this is still a problem, because the user might take much memory by
      executing many stored routines.
      
      The patch fixes this problem in the least-intrusive way. A soft limit
      (similar to the size of table definition cache) is introduced. To represent
      such limit the new runtime configuration parameter 'stored_program_cache'
      is introduced. The value of this parameter is stored in the new global
      variable stored_program_cache_size that used to control the size of SP-cache
      to overflow. 
      
      The parameter 'stored_program_cache' limits number of cached routines for
      each thread. It has the following min/default/max values given from support:
        min = 256, default = 256, max = 512 * 1024.
      Also it should be noted that this parameter limits the size of 
      each cache (for stored procedures and for stored functions) separately.
      
      The SP-cache size is checked after top-level statement is parsed.
      If SP-cache size exceeds the limit specified by parameter
      'stored_program_cache' then SP-cache is flushed and memory allocated for
      cache objects is freed. Such approach allows to flush cache safely 
      when there are dependencies among stored routines.
      
      
      sql/mysqld.cc:
        Added global variable stored_program_cache_size to store value of
        configuration parameter 'stored-program-cache'.
      sql/mysqld.h:
        Added declaration of global variable stored_program_cache_size.
      sql/sp_cache.cc:
        Extended interface for sp_cache by adding helper routine
        sp_cache_enforce_limit to control size of stored routines cache for
        overflow. Also added method enforce_limit into class sp_cache that
        implements control of cache size for overflow.
      sql/sp_cache.h:
        Extended interface for sp_cache by adding standalone routine
        sp_cache_enforce_limit to control size of stored routines cache
        for overflow.
      sql/sql_parse.cc:
        Added flush of sp_cache after processing of next sql-statement
        received from a client.
      sql/sql_prepare.cc:
        Added flush of sp_cache after preparation/execution of next prepared
        sql-statement received from a client.
      sql/sys_vars.cc:
        Added support for configuration parameter stored-program-cache.
      076bf863
  25. 20 Dec, 2011 1 commit
  26. 12 Dec, 2011 1 commit
    • Sergei Golubchik's avatar
      after merge changes: · 4ae652e5
      Sergei Golubchik authored
      * rename all debugging related command-line options
        and variables to start from "debug-", and made them all
        OFF by default.
      * replace "MySQL" with "MariaDB" in error messages
      * "Cast ... converted ... integer to it's ... complement"
        is now a note, not a warning
      * @@query_cache_strip_comments now has a session scope,
        not global.
      4ae652e5
  27. 28 Nov, 2011 1 commit
  28. 15 Nov, 2011 1 commit
    • Dmitry Lenev's avatar
      Fix for bug#12695572 - "IMPROVE MDL PERFORMANCE IN PRE-VISTA · a3957a43
      Dmitry Lenev authored
      BY CACHING OR REDUCING CREATEEVENT CALLS".
       
      5.5 versions of MySQL server performed worse than 5.1 versions 
      under single-connection workload in autocommit mode on Windows XP.
       
      Part of this slowdown can be attributed to overhead associated
      with constant creation/destruction of MDL_lock objects in the MDL
      subsystem. The problem is that creation/destruction of these
      objects causes creation and destruction of associated
      synchronization primitives, which are expensive on Windows XP.
       
      This patch tries to alleviate this problem by introducing a cache
      of unused MDL_object_lock objects. Instead of destroying such
      objects we put them into the cache and then reuse with a new
      key when creation of a new object is requested.
      
      To limit the size of this cache, a new --metadata-locks-cache-size
      start-up parameter was introduced.
      
      mysql-test/r/mysqld--help-notwin.result:
        Updated test after adding --metadata-locks-cache-size
        parameter.
      mysql-test/r/mysqld--help-win.result:
        Updated test after adding --metadata-locks-cache-size
        parameter.
      mysql-test/suite/sys_vars/r/metadata_locks_cache_size_basic.result:
        Added test coverage for newly introduced --metadata_locks_cache_size
        start-up parameter and corresponding global read-only variable.
      mysql-test/suite/sys_vars/t/metadata_locks_cache_size_basic-master.opt:
        Added test coverage for newly introduced --metadata_locks_cache_size
        start-up parameter and corresponding global read-only variable.
      mysql-test/suite/sys_vars/t/metadata_locks_cache_size_basic.test:
        Added test coverage for newly introduced --metadata_locks_cache_size
        start-up parameter and corresponding global read-only variable.
      sql/mdl.cc:
        Introduced caching of unused MDL_object_lock objects, in order to
        avoid costs associated with constant creation and destruction of
        such objects in single-connection workloads run in autocommit mode.
        Such costs can be pretty high on systems where creation and 
        destruction of synchronization primitives require a system call 
        (e.g. Windows XP).
         
        To implement this cache,a list of unused MDL_object_lock instances 
        was added to MDL_map object. Instead of being destroyed 
        MDL_object_lock instances are put into this list and re-used later 
        when creation of a new instance is required. Also added 
        MDL_lock::m_version counter to allow threads having outstanding 
        references to an MDL_object_lock instance to notice that it has 
        been moved to the unused objects list.
         
        Added a global variable for a start-up parameter that limits
        the size of the unused objects list.
         
        Note that we don't cache MDL_scoped_lock objects since they
        are supposed to be created only during execution of DDL 
        statements and therefore should not affect performance much.
      sql/mdl.h:
        Added a global variable for start-up parameter that limits the
        size of the unused MDL_object_lock objects list and constant
        for its default value.
      sql/sql_plist.h:
        Added I_P_List<>::pop_front() function.
      sql/sys_vars.cc:
        Introduced --metadata-locks-cache-size start-up parameter
        for specifying size of the cache of unused MDL_object_lock
        objects.
      a3957a43
  29. 28 Oct, 2011 1 commit
  30. 12 Jul, 2011 1 commit
  31. 02 Jul, 2011 1 commit
  32. 25 Apr, 2011 1 commit
  33. 14 Jan, 2011 1 commit
    • Guilhem Bichot's avatar
      Fix for BUG#59432 "--autocommit=on does not work (@@global.autocommit is 0)" · 3ddfad4a
      Guilhem Bichot authored
      mysql-test/r/mysqld--help-notwin.result:
        consequence of introducing opt_autocommit and its default
      mysql-test/suite/sys_vars/r/autocommit_func4.result:
        Before this fix, this test would have shown @@global.autocommit == 0
        in spite of --autocommit=on.
      mysql-test/suite/sys_vars/r/autocommit_func5.result:
        result unchanged by the fix
      sql/mysqld.cc:
        atoi(argument) was reliable for =0|1 parameters. Now that boolean options
        must support =on/off/true/false, atoi(argument) is wrong (being always 0
        for those strings). Instead, let the internal logic of my_getopt
        (in particular get_bool_argument()) set a boolean opt_autocommit
        properly, and use that to set global_system_variables.option_bits.
      3ddfad4a
  34. 05 Nov, 2010 2 commits
    • Alfranio Correia's avatar
      BUG#57275 binlog_cache_size affects trx- and stmt-cache and gets twice the expected memory · 12776efb
      Alfranio Correia authored
            
      After the WL#2687, the binlog_cache_size and max_binlog_cache_size affect both the
      stmt-cache and the trx-cache. This means that the resource used is twice the amount
      expected/defined by the user.
            
      The binlog_cache_use is incremented when the stmt-cache or the trx-cache is used
      and binlog_cache_disk_use is incremented when the disk space from the stmt-cache or the
      trx-cache is used. This behavior does not allow to distinguish which cache may be harming
      performance due to the extra disk accesses and needs to have its in-memory cache
      increased.
            
      To fix the problem, we introduced two new options and status variables related to the
      stmt-cache:
            
        Options:
            
          . binlog_stmt_cache_size
          . max_binlog_stmt_cache_size
            
          Status Variables:
            
          . binlog_stmt_cache_use
          . binlog_stmt_cache_disk_use
      
      So there are
      
        . binlog_cache_size that defines the size of the transactional cache for
        updates to transactional engines for the binary log.
      
        . binlog_stmt_cache_size that defines the size of the statement cache for
        updates to non-transactional engines for the binary log.
      
        . max_binlog_cache_size that sets the total size of the transactional
        cache.
      
        . max_binlog_stmt_cache_size that sets the total size of the statement
        cache.
      
        . binlog_cache_use that identifies the number of transactions that used the
        temporary transactional binary log cache.
      
        . binlog_cache_disk_use that identifies the number of transactions that used
        the temporary transactional binary log cache but that exceeded the value of
        binlog_cache_size.
      
        . binlog_stmt_cache_use that identifies the number of statements that used the
        temporary non-transactional binary log cache.
      
        . binlog_stmt_cache_disk_use that identifies the number of statements that used
        the temporary non-transactional binary log cache but that exceeded the value of
        binlog_stmt_cache_size.
      
      include/my_sys.h:
        Updated message on disk_writes' usage.
      mysql-test/extra/binlog_tests/binlog_cache_stat.test:
        Updated the test case and added code to check the new status variables
        binlog_stmt_cache_use and binlog_stmt_cache_disk_use.
      mysql-test/extra/rpl_tests/rpl_binlog_max_cache_size.test:
        Updated the test case to use the new system variables max_binlog_stmt_cache_size and binlog_stmt_cache_size.
      mysql-test/r/mysqld--help-notwin.result:
        Updated the result file.
      mysql-test/suite/binlog/r/binlog_mixed_cache_stat.result:
        Updated the result file.
      mysql-test/suite/binlog/r/binlog_row_cache_stat.result:
        Updated the result file.
      mysql-test/suite/binlog/r/binlog_stm_cache_stat.result:
        Updated the result file.
      mysql-test/suite/rpl/r/rpl_mixed_binlog_max_cache_size.result:
        Update the result file.
      mysql-test/suite/rpl/r/rpl_row_binlog_max_cache_size.result:
        Update the result file.
      mysql-test/suite/rpl/r/rpl_stm_binlog_max_cache_size.result:
        Updated the result file.
      mysql-test/suite/sys_vars/inc/binlog_stmt_cache_size_basic.inc:
        Added a test case to check the binlog_stmt_cache_size.
      mysql-test/suite/sys_vars/r/binlog_stmt_cache_size_basic_32.result:
        Updated the result file.
      mysql-test/suite/sys_vars/r/binlog_stmt_cache_size_basic_64.result:
        Updated the result file.
      mysql-test/suite/sys_vars/r/max_binlog_stmt_cache_size_basic.result:
        Updated the result file.
      mysql-test/suite/sys_vars/t/binlog_stmt_cache_size_basic_32.test:
        Added a test case to check the binlog_stmt_cache_size.
      mysql-test/suite/sys_vars/t/binlog_stmt_cache_size_basic_64.test:
        Added a test case to check the binlog_stmt_cache_size.
      mysql-test/suite/sys_vars/t/max_binlog_cache_size_func-master.opt:
        Removed because there is no test case max_binlog_cache_size_func.
      mysql-test/suite/sys_vars/t/max_binlog_stmt_cache_size_basic.test:
        Added a test case to check the system variable max_binlog_stmt_cache_size.
      sql/log.cc:
        There two main changes in here:
        
          . Changed the set_write_error() as an error message is set according
          to the type of the cache.
        
          . Created the function set_binlog_cache_info where references to the
          appropriate status and system variables are set and the server can
          smoothly compute statistics and set the maximum size for each cache.
      sql/log.h:
        Changed the signature of the function in order to identify the error message
        to be printed out as there is a different error code for each type of cache.
      sql/mysqld.cc:
        Added new status variables binlog_stmt_cache_use and binlog_stmt_cache_disk_use.
      sql/mysqld.h:
        Added new system variables max_binlog_stmt_cache_size and binlog_stmt_cache_size.
      sql/share/errmsg-utf8.txt:
        Added new error message related to the statement cache.
      sql/sys_vars.cc:
        Added new system variables max_binlog_stmt_cache_size and binlog_stmt_cache_size.
      12776efb
    • Guilhem Bichot's avatar
      Fix for BUG#57316 "It is not clear how to disable autocommit" · 73eef0a7
      Guilhem Bichot authored
      add boolean command-line option --autocommit.
      
      mysql-test/mysql-test-run.pl:
        do in --gdb like in --ddd: to let the developer debug the startup
        phase (like command-line options parsing), don't "run".
        It's the third time I do this change, it was previously lost
        by merges, port of 6.0 to next-mr...
      mysql-test/r/mysqld--help-notwin.result:
        new command-line option
      mysql-test/r/mysqld--help-win.result:
        a Linux user's best guess at what the Windows result should be
      mysql-test/suite/sys_vars/inc/autocommit_func2.inc:
        new test
      mysql-test/suite/sys_vars/t/autocommit_func2-master.opt:
        test new option
      mysql-test/suite/sys_vars/t/autocommit_func3-master.opt:
        test new option
      sql/mysqld.cc:
        new --autocommit
      sql/mysqld.h:
        new --autocommit
      sql/sql_partition.cc:
        What matters to this partitioning quote is to have
        the OPTION_QUOTE_SHOW_CREATE flag down, it's all
        that append_identifier() uses. So we make it explicit.
      73eef0a7
  35. 30 Sep, 2010 1 commit
  36. 28 Aug, 2010 1 commit
  37. 18 Aug, 2010 1 commit
  38. 17 Jun, 2010 1 commit
    • Magne Mahre's avatar
      WL#5349 Change default storage engine to InnoDB · 6884c955
      Magne Mahre authored
      The default storage engine is changed from MyISAM to
      InnoDB, in all builds except for the embedded server.
      
      In addition, the following system variables are 
      changed:
      
        * innodb_file_per_table is enabled
        * innodb_strict_mode is enabled
        * innodb_file_format_name_update is changed
          to 'Barracuda'
      
      The test suite is changed so that tests that do not
      explicitly include the have_innodb.inc are run with
      --default-storage-engine=MyISAM.  This is to ease the
      transition, so that most regression tests are run
      with the same engine as before.
      
      Some tests are disabled for the embedded server
      regression test, as the output of certain statements
      will be different that for the regular server
      (i.e SELECT @@default_storage_engine).  This is to
      ease transition.
      
      
      
      mysql-test/mysql-test-run.pl:
        The regression test suite now adds a
        --default-storage-engine=MyISAM for all non-innodb 
        tests.  This behaviour can be controlled by the
        default-myisam switch in mysql-test-run
      mysql-test/t/bootstrap-master.opt:
        The bootstrap test can only be run without InnoDB
        as it starts several mysqld instances on the same
        datadir. This is possible with MyISAM, but not
        with InnoDB.
      storage/innobase/CMakeLists.txt:
        Build InnoDB per default
      storage/innobase/handler/ha_innodb.cc:
        Change default values for system variables
        
          Enable file_per_table
          Enable strict_mode
          Upgrade default file format to Barracuda
      6884c955