1. 27 Aug, 2014 2 commits
    • Sergei Petrunia's avatar
      MDEV-6384: It seems like OPTIMIZER take into account the order of indexes in the table · f1a16833
      Sergei Petrunia authored
      When ORDER BY ... LIMIT check whether it should switch from index IDX1
      to index IDX2, it should not ignore the fact that IDX2 may have a
      potential range or ref(const) access.
      Istead, it should calculate their costs: there is now a saved range
      optimizer cost and code to re-calculate what best_access_path()
      calculated for ref(const).
      
      /* in current cost model these two can be very different
      numbers unfortunately */
      f1a16833
    • Sergei Petrunia's avatar
      MDEV-6480: Remove conditions for which range optimizer returned SEL_ARG::IMPOSSIBLE · be00e279
      Sergei Petrunia authored
      Let range optimizer remove parts of OR-clauses for which range analysis
      produced SEL_TREE(IMPOSSIBLE).
      There is no need to remove parts of AND-clauses: either they are inside
      of OR (and the whole AND-clause will be removed), or the AND-clause is
      at the top level, in which case the whole WHERE (or ON) is always FALSE
      and this is a degenerate case which receives special treatment.
      
      The removal process takes care not to produce 1-way ORs (in that case
      we substitute the OR for its remaining member).
      be00e279
  2. 26 Aug, 2014 2 commits
  3. 24 Aug, 2014 1 commit
  4. 19 Aug, 2014 1 commit
    • Sergey Vojtovich's avatar
      MDEV-4262 - P_S discovery · f1c1c04a
      Sergey Vojtovich authored
      Discover P_S tables automatically.
      
      Most of this patch is code clean-up:
      - removed tests and code responsible for P_S tables correctness verification
      - always return error from ha_perfschema::create()
      - install/upgrade scripts won't create P_S tables anymore
      f1c1c04a
  5. 18 Aug, 2014 2 commits
  6. 13 Aug, 2014 4 commits
  7. 09 Aug, 2014 4 commits
    • Monty's avatar
      Made sql_log_slow a session variable · e2b2bde3
      Monty authored
      mysqldump:
      - Added --log-queries to allow one to disable logging for the dump
      
      sql/log_event.cc:
      - Removed setting of enable_slow_log as it's not required anymore.
      
      sql/sql_parse.cc:
      - Set enable_slow_log to value of thd->variables.sql_log_slow as this will speed up tests if slow log is disabled.
      - opt_log_slow_admin_statements can now only disable slow log, not enable it.
      
      sql/sql_explain.cc:
      - Minor cleanup
      
      Other things:
      - Added sql_log_slow to system variables.
      - Changed opt_slow_log to global_system_variables.sql_log_slow in all files
      - Updated tests to reflect changes
      e2b2bde3
    • Monty's avatar
      Changes for using build scripts · 7375f025
      Monty authored
      Removed -DSECURITY_HARDENED=OFF for debug build scripts
      ignore configure
      7375f025
    • Monty's avatar
      Change MySQL -> MariaDB inc scripts · b4c74e2a
      Monty authored
      b4c74e2a
    • Monty's avatar
      Minor cleanups, fix compiler warnings · 3bde1393
      Monty authored
      3bde1393
  8. 07 Aug, 2014 2 commits
  9. 06 Aug, 2014 1 commit
    • Jan Lindström's avatar
      MDEV-5834: Merge Kakao Defragmentation implementation to MariaDB 10.1 · 6dad23f0
      Jan Lindström authored
          Merge https://github.com/kakao/mariadb-10.0 that contains Facebook's
          implementation for defragmentation
      
          facebook/mysql-5.6@a2d3a74
          facebook/mysql-5.6@def96c8
          facebook/mysql-5.6@9c67c5d
          facebook/mysql-5.6@921a81b
          facebook/mysql-5.6@aa519bd
          facebook/mysql-5.6@fea7d13
          facebook/mysql-5.6@09b29d3
          facebook/mysql-5.6@9284abb
          facebook/mysql-5.6@dbd623d
          facebook/mysql-5.6@aed55dc
          facebook/mysql-5.6@aad5c82
      
          This version does not add new SQL-syntax and new handler API function.
          Instead optimize table is mapped to defragment table if
          innodb_defragment=ON, by default the feature is off.
      
          Contains changes authored by Sunguck Lee (Kakao).
      6dad23f0
  10. 31 Jul, 2014 1 commit
    • Jan Lindström's avatar
      MDEV-6512: InnoDB: Assertion failure in thread 4537024512 in file · e974b564
      Jan Lindström authored
      buf0buf.cc line 2642.
      
      Analysis: innodb_compression_algorithm is a global variable and
      can change while we are building page compressed page. This could
      lead page corruption.
      
      Fix: Cache innodb_compression_algorithm on local variable before
      doing any compression or page formating to avoid concurrent
      change. Improved page verification on debug builds.
      e974b564
  11. 29 Jul, 2014 1 commit
  12. 25 Jul, 2014 2 commits
    • Jan Lindström's avatar
      Fix compiler error on Windows. · 1f69ff44
      Jan Lindström authored
      1f69ff44
    • Jan Lindström's avatar
      Fiix random test failures on fil_decompress_page_2 function. · 56c4b016
      Jan Lindström authored
      Analysis: InnoDB writes also files that do not contain FIL-header.
      This could lead incorrect analysis on os_fil_read_func function
      when it tries to see is page page compressed based on FIL_PAGE_TYPE
      field on FIL-header. With bad luck uncompressed page that does
      not contain FIL-headed, the byte on FIL_PAGE_TYPE position could
      indicate that page is page comrpessed.
      
      Fix: Upper layer must indicate is file space page compressed
      or not. If this is not yet known, we need to read the FIL-header
      and find it out. Files that we know that are not page compressed
      we can always just provide FALSE.
      56c4b016
  13. 23 Jul, 2014 9 commits
  14. 22 Jul, 2014 2 commits
  15. 05 Jul, 2014 1 commit
  16. 04 Jul, 2014 1 commit
  17. 02 Jul, 2014 1 commit
  18. 29 Jun, 2014 1 commit
  19. 28 Jun, 2014 1 commit
    • Jan Lindström's avatar
      MDEV-6376: InnoDB: Assertion failure in thread 139995225970432 · b35c5912
      Jan Lindström authored
      in file buf0mtflu.cc line 570.
      
      Analysis: Real timing bug, we should take the mutex before we
      try to send those shutdown messages, that would make sure
      that threads doing a unfinished flush (they have acquired
      this mutex) have time to do their work before we add shutdown
      messages to work queue. Currently, we just add those shutdown
      messages to work queue and code assumes that at flush, there
      is constant number of items to be processed and thus
      leading to assertion.
      b35c5912
  20. 27 Jun, 2014 1 commit