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_parse.cc
Find file BlameHistoryPermalink
  • Sergey Petrunya's avatar
    MDEV-3798: [SHOW] EXPLAIN UPDATE/DELETE, Memory leak in binlog.binlog_base64_flag: · 4bed7aa8
    Sergey Petrunya authored Oct 16, 2013
    - It turns out, there are statements that will call lex_start(thd->lex) 
      after parsing has been finished. lex_start() will set lex->explain=NULL,
      which will lose the pointer to already allocated Explain_plan object.
    - To get rid of this, switch to lazy creation of lex->explain.  Now, it is 
      created only when we get a part ot query plan.
    4bed7aa8
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7