An error occurred fetching the project authors.
  1. 29 Sep, 2009 1 commit
    • Ingo Struewing's avatar
      WL#4259 - Debug Sync Facility · 21586dfb
      Ingo Struewing authored
      Backport from 6.0 to 5.1.
      Only those sync points are included, which are used in debug_sync.test.
      
        The Debug Sync Facility allows to place synchronization points
        in the code:
        
        open_tables(...)
        
        DEBUG_SYNC(thd, "after_open_tables");
        
        lock_tables(...)
        
        When activated, a sync point can
        
        - Send a signal and/or
        - Wait for a signal
        
        Nomenclature:
        
        - signal:            A value of a global variable that persists
                             until overwritten by a new signal. The global
                             variable can also be seen as a "signal post"
                             or "flag mast". Then the signal is what is
                             attached to the "signal post" or "flag mast".
        
        - send a signal:     Assign the value (the signal) to the global
                             variable ("set a flag") and broadcast a
                             global condition to wake those waiting for
                             a signal.
        
        - wait for a signal: Loop over waiting for the global condition until
                             the global value matches the wait-for signal.
        
        Please find more information in the top comment in debug_sync.cc
        or in the worklog entry.
      21586dfb
  2. 23 Sep, 2009 1 commit
  3. 22 Sep, 2009 1 commit
    • Davi Arnaut's avatar
      Bug#45498: Socket variable not available on Windows · 0e7242d8
      Davi Arnaut authored
      The "socket" variable is not available on Windows even though
      the --socket option can be used to specify the pipe name for
      local connections that use a named pipe.
      
      The solution is to ensure that the variable is always defined.
      0e7242d8
  4. 10 Sep, 2009 1 commit
  5. 16 Jul, 2009 1 commit
  6. 19 Jun, 2009 1 commit
    • Staale Smedseng's avatar
      Bug #32223 SETting max_allowed_packet variable · 2b48caa4
      Staale Smedseng authored
            
      Inconsistent behavior of session variable max_allowed_packet 
      (and net_buffer_length); only assignment to the global variable 
      has any effect, without this being obvious to the user.
            
      The patch for Bug#22891 is backported to 5.0, making the two
      session variables read-only. As this is a backport to GA 
      software, the error used when trying to assign to the read-
      only variable is ER_UNKNOWN_ERROR. The error message is the 
      same as in 5.1+.
      2b48caa4
  7. 15 May, 2009 1 commit
    • Satya B's avatar
      Fix for BUG#10206 - InnoDB: Transaction requiring Max_BinLog_Cache_size > 4GB · fe5121af
      Satya B authored
                          always rollsback.
      
      The global variable max_binlog_cache_size cannot be set more than 4GB on
      32 bit systems, limiting transactions of all storage engines to 4G of changes.
      
      The problem is max_binlog_cache_size is declared as ulong which is 4 bytes
      on 32 bit and 8 bytes on 64 bit machines.
      
      Fixed by using ulonglong for max_binlog_cache_size which is 8bytes on 32 
      and 64 bit machines.The range for max_binlog_cache_size on 32 bit and 64 bit
      systems is 4096-18446744073709547520 bytes.
      fe5121af
  8. 11 May, 2009 1 commit
  9. 05 May, 2009 1 commit
  10. 30 Apr, 2009 1 commit
  11. 24 Apr, 2009 1 commit
  12. 16 Mar, 2009 1 commit
  13. 14 Mar, 2009 1 commit
  14. 11 Mar, 2009 2 commits
  15. 05 Mar, 2009 2 commits
  16. 27 Feb, 2009 1 commit
    • Tatiana A. Nurnberg's avatar
      Bug#40657: assertion with out of range variables and traditional sql_mode · e3233c25
      Tatiana A. Nurnberg authored
      In STRICT mode, out-of-bounds values caused an error message
      to be queued (rather than just a warning), without any further
      error-like processing happening. (The error is queued during
      update, at which time it's too late. For it to be processed
      properly, it would need to be queued during check-stage.)
      The assertion rightfully complains that we're trying to send
      an OK while having an error queued.
      
      Changeset breaks a lot of tests out into check-stage. This also
      allows us to send more correct warnings/error messages.
      e3233c25
  17. 24 Feb, 2009 1 commit
    • Tatiana A. Nurnberg's avatar
      Bug#40657: assertion with out of range variables and traditional sql_mode · 76e063b9
      Tatiana A. Nurnberg authored
      In STRICT mode, out-of-bounds values caused an error message
      to be queued (rather than just a warning), without any further
      error-like processing happening. (The error is queued during
      update, at which time it's too late. For it to be processed
      properly, it would need to be queued during check-stage.)
      The assertion rightfully complains that we're trying to send
      an OK while having an error queued.
      
      Changeset breaks a lot of tests out into check-stage. This also
      allows us to send more correct warnings/error messages.
      76e063b9
  18. 23 Feb, 2009 1 commit
  19. 16 Feb, 2009 1 commit
  20. 10 Feb, 2009 1 commit
  21. 09 Feb, 2009 1 commit
  22. 03 Feb, 2009 1 commit
    • Tatiana A. Nurnberg's avatar
      Bug#40657: assertion with out of range variables and traditional sql_mode · 3b9132fd
      Tatiana A. Nurnberg authored
      In STRICT mode, out-of-bounds values caused an error message
      to be queued (rather than just a warning), without any further
      error-like processing happening. (The error is queued during
      update, at which time it's too late. For it to be processed
      properly, it would need to be queued during check-stage.)
      The assertion rightfully complains that we're trying to send
      an OK while having an error queued.
      
      Changeset breaks a lot of tests out into check-stage. This also
      allows us to send more correct warnings/error messages.
      3b9132fd
  23. 08 Jan, 2009 1 commit
    • Timothy Smith's avatar
      Fix a few problems after latest bunch of InnoDB snapshot changes: · e6100a22
      Timothy Smith authored
      The binlog_innodb test was sensitive to what tests ran before it.  Now run
      FLUSH STATUS before performing operations that need to be checked.
      
      sys_var_thd_ulong::update() was improperly casting an option value from
      ulonglong to ulong before comparing it to the max allowed value.  On systems
      where ulong and ulonglong are of different size, this caused values greater
      than ULONG_MAX to wrap around (not be truncated to ULONG_MAX, which appears to
      have been the intention of the original coder), and caused some checks to work
      incorrectly.  This wasn't generally visible to the user, because later checks
      would prevent the wrapped-around value from being used.  But it caused warning
      messages to differ between 32- and 64-bit platforms.  Fix is to just remove the
      cast.  Also added a DBUG_ASSERT to ensure that the value really is capped
      properly before finally stuffing it into the ulong.
      e6100a22
  24. 24 Dec, 2008 1 commit
  25. 28 Nov, 2008 1 commit
    • Georgi Kodinov's avatar
      Bug #37339: SHOW VARIABLES not working properly with multi-byte datadir · 0708ad5f
      Georgi Kodinov authored
            
      The SHOW VARIABLES LIKE .../SELECT @@/SELECT ... FROM INFORMATION_SCHEMA.VARIABLES
      were assuming that all the system variables are in system charset (UTF-8).
      However the variables that are settable through command line will have a different
      character set (character_set_filesystem).
      Fixed the server to remember the correct character set of basedir, datadir, tmpdir,
      ssl, plugin_dir, slave_load_tmpdir, innodb variables; init_connect and init_slave 
      variables and use it when processing data.
      0708ad5f
  26. 21 Nov, 2008 1 commit
    • Ingo Struewing's avatar
      Bug#28234 - global/session scope - documentation vs implementation · 3ea68493
      Ingo Struewing authored
      Several system variables did not behave like system variables should do.
      When trying to SET them or use them in SELECT, they were reported as
      "unknown system variable". But they appeared in SHOW VARIABLES.
      
      This has been fixed by removing the "fixed_vars" array of variables
      and integrating the variables into the normal system variables chain.
      All of these variables do now behave as read-only global-only
      variables. Trying to SET them tells they are read-only, trying to
      SELECT the session value tells they are global only. Selecting the
      global value works. It delivers the same value as SHOW VARIABLES.
      3ea68493
  27. 20 Nov, 2008 1 commit
    • Staale Smedseng's avatar
      A fix for Bug#22891 "session level max_allowed_packet can be · e60c8c8b
      Staale Smedseng authored
      set but is ignored".
                                        
      This patch makes @@session.max_allowed_packed and
      @@session.net_buffer_length read-only as suggested in the bug
      report. The user will have to use SET GLOBAL (and reconnect)
      to alter the session values of these variables.
                                  
      The error string ER_VARIABLE_IS_READONLY is introduced.
                                  
      Tests are modified accordingly.
      e60c8c8b
  28. 10 Nov, 2008 1 commit
  29. 23 Oct, 2008 1 commit
  30. 08 Oct, 2008 1 commit
    • Georgi Kodinov's avatar
      Bug #32124: crash if prepared statements refer to variables in the where clause · 489ad44a
      Georgi Kodinov authored
                        
      The code to get read the value of a system variable was extracting its value 
      on PREPARE stage and was substituting the value (as a constant) into the parse tree.
      Note that this must be a reversible transformation, i.e. it must be reversed before
      each re-execution.
      Unfortunately this cannot be reliably done using the current code, because there are
      other non-reversible source tree transformations that can interfere with this
      reversible transformation.
      Fixed by not resolving the value at PREPARE, but at EXECUTE (as the rest of the 
      functions operate). Added a cache of the value (so that it's constant throughout
      the execution of the query). Note that the cache also caches NULL values.
      Updated an obsolete related test suite (variables-big) and the code to test the 
      result type of system variables (as per bug 74).
      489ad44a
  31. 06 Oct, 2008 1 commit
    • Tatiana A. Nurnberg's avatar
      WL#4403 deprecate @log and @slow_log_queries variables · c1ed70d3
      Tatiana A. Nurnberg authored
      Adds --general_log_file, --slow_query_log_file command-
      line options to match system variables of the same names.
      
      Deprecates --log, --log-slow-queries command-line options
      and log, log_slow_queries system-variables for v7.0; they
      are superseded by general_log/general_log_file and
      slow_query_log/slow_query_log_file, respectively.
      c1ed70d3
  32. 09 Sep, 2008 1 commit
    • Mats Kindahl's avatar
      Bug #39106: · 69a8281c
      Mats Kindahl authored
      SUPER is not required to change binlog format for session
      
      A user without SUPER privileges can change the value of the
      session variable BINLOG_FORMAT, causing problems for a DBA.
      
      This changeset requires a user to have SUPER privileges to
      change the value of the session variable BINLOG_FORMAT, and
      not only the global variable BINLOG_FORMAT.
      69a8281c
  33. 25 Aug, 2008 1 commit
  34. 28 Jul, 2008 1 commit
    • Alexey Botchkov's avatar
      Bug#37428 Potential security issue with UDFs - linux shellcode execution. · 5237d244
      Alexey Botchkov authored
            
            plugin_dir option backported from 5.1
      
      per-file messages:
        sql/mysql_priv.h
          Bug#37428 Potential security issue with UDFs - linux shellcode execution.
          
          opt_plugin_dir and opt_plugin_dir_ptr declared.
        sql/mysqld.cc
          Bug#37428 Potential security issue with UDFs - linux shellcode execution.
          
          'plugin_dir' option added
        sql/set_var.cc
          Bug#37428 Potential security issue with UDFs - linux shellcode execution.
          
          'plugin_dir' option added.
        sql/sql_udf.cc
          Bug#37428 Potential security issue with UDFs - linux shellcode execution.
          
          opt_plugin_dir added to the udf->dl path. Warn if it's not specified.
        sql/unireg.h
          Bug#37428 Potential security issue with UDFs - linux shellcode execution.
          
          PLUGINDIR defined.
      5237d244
  35. 17 Jul, 2008 1 commit
  36. 16 Jul, 2008 1 commit
  37. 19 Jun, 2008 1 commit
  38. 09 May, 2008 1 commit