1. 07 Mar, 2008 1 commit
  2. 06 Mar, 2008 2 commits
  3. 04 Mar, 2008 1 commit
  4. 27 Feb, 2008 1 commit
  5. 24 Feb, 2008 1 commit
  6. 22 Feb, 2008 1 commit
    • svoj@mysql.com/june.mysql.com's avatar
      BUG#13861 - START SLAVE UNTIL may stop 1 evnt too late if · fe3b1c8e
      svoj@mysql.com/june.mysql.com authored
                  log-slave-updates and circul repl
      
      Slave SQL thread may execute one extra event when there are events
      skipped by slave I/O thread (e.g. originated by the same server).
      Whereas it was requested not to do so by the UNTIL condition.
      
      This happens because we compare with the end position of previously
      executed event. This is fine when there are no skipped by slave I/O
      thread events, as end position of previous event equals to start
      position of to be executed event. Otherwise this position equals to
      start position of skipped event.
      
      This is fixed by:
      - reading the event to be executed before checking if the until condition
        is satisfied.
      - comparing the start position of the event to be executed. Since we do
        not have the start position available, we compute it by subtracting
        event length from end position (which is available).
      - if there are no events on the event queue at the slave sql starting
        time, that meet until condition, we stop immediately, as in this
        case we do not want to wait for next event.
      fe3b1c8e
  7. 21 Feb, 2008 1 commit
  8. 19 Feb, 2008 1 commit
  9. 15 Feb, 2008 2 commits
  10. 14 Feb, 2008 4 commits
  11. 12 Feb, 2008 2 commits
  12. 11 Feb, 2008 4 commits
  13. 08 Feb, 2008 2 commits
  14. 07 Feb, 2008 2 commits
  15. 06 Feb, 2008 4 commits
  16. 05 Feb, 2008 1 commit
    • aelkin/elkin@koti.dsl.inet.fi's avatar
      Bug #34305 show slave status handling segfaults when slave io is about · 51b33ea3
      aelkin/elkin@koti.dsl.inet.fi authored
          to leave
      
      The artifact was caused by
      a flaw in concurrent accessing the slave's io thd by
      the io itself and a handling show slave status thread.
      Namely, show_master_info did not acquire mi->run_lock mutex that is
      specified for mi->io_thd member.
      
      Fixed with deploying the mutex locking and unlocking. The mutex is kept
      short time and without interleaving with mi->data_lock mutex.
      
      Todo: to report and fix an issue with 
          sys_var_slave_skip_counter::{methods} 
      seem to acquire incorrectly
           active_mi->rli.run_lock
      instead of the specified
           active_mi->rli.data_lock
      
      A test case is difficult to compose, so rpl_packet should continue serving
      as the indicator.
      51b33ea3
  17. 04 Feb, 2008 4 commits
  18. 01 Feb, 2008 6 commits