Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • M mariadb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • mariadb
  • Repository
  • mariadb
  • sql
  • sql_repl.cc
Find file BlameHistoryPermalink
  • aelkin/elkin@koti.dsl.inet.fi's avatar
    Bug #31359 change_master sets group_master_log_pos twice, · 10320385
    aelkin/elkin@koti.dsl.inet.fi authored Dec 21, 2007
                ignores future_group_master_log_p
    
    There was a redundant assignement. However, that's the only artifact.
    Wrt to future_group_master_log_position, there is no issue.
    The counter is supposed to be set at Log_event::exec_event().
    It's used only by Innodb for recovery purposes.
    10320385
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7