1. 14 Sep, 2016 1 commit
  2. 13 Sep, 2016 1 commit
  3. 12 Sep, 2016 17 commits
  4. 04 Sep, 2016 2 commits
  5. 25 Aug, 2016 3 commits
  6. 19 Aug, 2016 2 commits
  7. 18 Aug, 2016 1 commit
  8. 08 Aug, 2016 2 commits
    • Nirbhay Choubey's avatar
      MDEV-10320: NO-OP ALTER TABLE on temporary tables getting · 69052ed0
      Nirbhay Choubey authored
      .. logged under row binlog format
      
      In the early stages of ALTER TABLE execution, the implementation
      checks whether its a NOOP (alter_info->flags == 0), and if so,
      it returns after logging the command to binary log. The logging,
      however, was done unconditionally.
      
      Fixed by skipping the logging for temporary tables when under row
      based replication.
      69052ed0
    • Nirbhay Choubey's avatar
      MDEV-10216: Assertion `strcmp(share->unique_file_name,filename) || · df9b4554
      Nirbhay Choubey authored
      .. share->last_version' failed in myisam/mi_open.c:67: test_if_reopen
      
      During the RENAME operation since the renamed temporary table is also
      opened and added to myisam_open_list/maria_open_list, resetting the
      last_version at the end of operation (HA_EXTRA_PREPARE_FOR_RENAME)
      will cause an assertion failure when a subsequent query tries to open
      an additional temporary table instance and thus attempts to reuse it
      from the open table list.
      
      This commit fixes the issue by skipping flush/close operations executed
      toward the end of ALTER for temporary tables. It also enables a shortcut
      for simple ALTERs (like rename, disable/enable keys) on temporary
      tables.
      
      As safety checks, added some assertions at code points that should not
      be hit for temporary tables.
      df9b4554
  9. 05 Aug, 2016 4 commits
  10. 04 Aug, 2016 1 commit
  11. 03 Aug, 2016 2 commits
  12. 30 Jul, 2016 3 commits
  13. 25 Jul, 2016 1 commit
    • Kristian Nielsen's avatar
      MDEV-10271: Stopped SQL slave thread doesn't print a message to error log like IO thread does · fb076581
      Kristian Nielsen authored
      Make the slave SQL thread always output to the error log the message "Slave
      SQL thread exiting, replication stopped in ..." whenever it previously
      outputted "Slave SQL thread initialized, starting replication ...".
      
      Before this patch, it was somewhat inconsistent in which cases the message
      would be output and in which not, depending on the exact time and cause of
      the condition that caused the SQL thread to stop.
      fb076581