1. 06 Dec, 2017 5 commits
  2. 05 Dec, 2017 3 commits
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · 1d526f31
      Marko Mäkelä authored
      1d526f31
    • Marko Mäkelä's avatar
      MDEV-14587 dict_stats_process_entry_from_defrag_pool() fails to call... · 63cbb982
      Marko Mäkelä authored
      MDEV-14587 dict_stats_process_entry_from_defrag_pool() fails to call dict_table_close() when index==NULL
      
      dict_stats_process_entry_from_defrag_pool(): Simplify the logic,
      and always call dict_table_close() when dict_table_open() returned
      a non-NULL handle.
      63cbb982
    • Marko Mäkelä's avatar
      MDEV-13670/MDEV-14550 Error log flood : "InnoDB: page_cleaner: 1000ms... · d1ab8903
      Marko Mäkelä authored
      MDEV-13670/MDEV-14550 Error log flood :  "InnoDB: page_cleaner: 1000ms intended loop took N ms. The settings might not be optimal."
      
      Silence the error log output that was introduced in MySQL 5.7
      (MariaDB 10.2.2) if log_warnings=2 or less.
      
      We should still figure out what these messages really indicate
      and how to solve the problems.
      
      pc_sleep_if_needed(): Add a parameter for the current time,
      so that there will be fewer successive calls to ut_time_ms()
      with no I/O between them.
      
      buf_flush_page_cleaner_coordinator(): Exit the first loop
      whenever shutdown has been requested. At the start of the loop,
      call ut_time_ms() only once. Do not display the message if
      log_warnings=2 or less.
      d1ab8903
  3. 04 Dec, 2017 2 commits
  4. 03 Dec, 2017 2 commits
    • Monty's avatar
      MDEV-10688 rpl.rpl_row_log_innodb failed in buildbot · d7b0b8dd
      Monty authored
      Problem was that Binlog_checkpoint can happen at random times.
      Fixed by not write binlog_checkpoint for the rpl_log test.
      
      Other things:
      - Removed not used variable "$keep_gtid_events"
      - Added option for show_binlog_events to skip binlog_checkpoint
      d7b0b8dd
    • Monty's avatar
      resolve_stack_dump updated to match latest stack trace format · d9188ada
      Monty authored
      Originally only symbols withing [] where resolved. Now we resolve
      symbols also withing (+...)
      
      To make it easier to see where the resolved symbol comes from, we
      resolve the symbol 'in place' instead of just printing the resolved
      symbol alone.
      d9188ada
  5. 01 Dec, 2017 2 commits
  6. 30 Nov, 2017 1 commit
  7. 29 Nov, 2017 3 commits
  8. 28 Nov, 2017 3 commits
  9. 27 Nov, 2017 1 commit
  10. 24 Nov, 2017 9 commits
  11. 23 Nov, 2017 5 commits
  12. 22 Nov, 2017 4 commits