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
You need to sign in or sign up before continuing.
  • mariadb
  • sql
  • sql_repl.cc
Find file BlameHistoryPermalink
  • aelkin/elkin@dsl-hkigw8-fe00f800-98.dhcp.inet.fi's avatar
    BUG#19402 SQL close to the size of the max_allowed_packet fails on the slave · b4b06d7a
    aelkin/elkin@dsl-hkigw8-fe00f800-98.dhcp.inet.fi authored Sep 12, 2006
    A communication packet can also be a binlog event sent from the master to the slave.
    To be sent by master dump and accepted by slave io thread both have to have
    the value of max_allowed_packet bigger than one that client connection had.
    
    In the patch there is the MAX possible replicatio header size estimation for events
    in binlog that embedded user query. Only these events of query_log_event type, i.e
    just plain queries, require attention. 
    b4b06d7a
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7