Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • M MariaDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • MariaDB
  • Repository

Switch branch/tag
  • mariadb
  • storage
  • innobase
  • trx
  • trx0purge.cc
Find file BlameHistoryPermalink
  • Marko Mäkelä's avatar
    MDEV-33464 Crash when innodb_max_undo_log_size is set to innodb_page_size*4294967296 · 53c6c823
    Marko Mäkelä authored Feb 15, 2024
    purge_sys_t::truncating_tablespace(): Clamp the
    innodb_max_undo_log_size to the maximum number of pages
    before converting the result into a 32-bit unsigned integer.
    
    This fixes up commit f8c88d90 (MDEV-33213).
    
    In later major versions, we would use 32-bit unsigned integer here
    due to commit ca501ffb
    and the code would crash also on 64-bit processors.
    
    Reviewed by: Debarun Banerjee
    53c6c823

Replace trx0purge.cc

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7