1. 27 Jun, 2016 3 commits
  2. 24 Jun, 2016 1 commit
  3. 23 Jun, 2016 2 commits
  4. 22 Jun, 2016 1 commit
  5. 21 Jun, 2016 1 commit
  6. 19 Jun, 2016 1 commit
  7. 12 Jun, 2016 1 commit
  8. 08 Jun, 2016 2 commits
  9. 03 Jun, 2016 3 commits
  10. 02 Jun, 2016 6 commits
  11. 01 Jun, 2016 4 commits
  12. 31 May, 2016 1 commit
    • Sergei Petrunia's avatar
      MDEV-9764: MariaDB does not limit memory used for range optimization · 01679040
      Sergei Petrunia authored
      A partial backport of 67f21fb3a077dedfd14b9ca720e926c55e682f93,
      Bug#22283790: RANGE OPTIMIZER UTILIZES TOO MUCH MEMORY WITH MANY OR CONDITIONS
      
      The backported part changes SEL_TREE::keys from being an array of
      MAX_KEY elements (64*8=512 bytes) to a Mem_root_array<SEL_ARG*> (32 bytes +
      alloc'ed array of as many elements as we need).
      
      The patch doesn't fix the "not limiting memory" part, but the memory usage
      is much lower with it.
      01679040
  13. 30 May, 2016 4 commits
  14. 28 May, 2016 1 commit
  15. 27 May, 2016 1 commit
  16. 26 May, 2016 4 commits
  17. 23 May, 2016 1 commit
    • Sergei Petrunia's avatar
      MDEV-8989: ORDER BY optimizer ignores equality propagation · 99cd5a96
      Sergei Petrunia authored
      Variant #4 of the fix.
      
      Make ORDER BY optimization functions take into account multiple
      equalities. This is done in several places:
      - remove_const() checks whether we can sort the first table in the
        join, or we need to put rows into temp.table and then sort.
      - test_if_order_by_key() checks whether there are indexes that
        can be used to produce the required ordering
      - make_unireg_sortorder() constructs sort criteria for filesort.
      99cd5a96
  18. 18 May, 2016 1 commit
  19. 17 May, 2016 1 commit
  20. 11 May, 2016 1 commit