mysql是否会缓存执行计划

最新推荐文章于 2024-11-17 08:30:00 发布

原创最新推荐文章于 2024-11-17 08:30:00 发布 · 362 阅读

CC 4.0 BY-SA版权

博客探讨了MySQL中是否存在类似Oracle的硬解析和软解析概念，并指出MySQL的query cache并非缓存执行计划，而是缓存查询结果。尽管MySQL 8.0已移除了query cache功能。

网友问题了一个问题，oracle中有硬解析，软解析之分，mysql是否也有软解析？解析完sql后，后面不会再次重复解析？其实是有的就是query cache，认为query cache是缓存结果数据的，其实不是。然而query cache在8被删除了

/*
    Warning.
    The purpose of query_cache_send_result_to_client() is to lookup the
    query in the query cache first, to avoid parsing and executing it.
    So, the natural implementation would be to:
    - first, call query_cache_send_result_to_client,
    - second, if caching failed, initialise the lexical and syntactic parser.
    The problem is that the query cache depends on a clean initialization
    of (among others) lex->safe_to_cache_query and thd->server_status,
    which are reset respectively in
    - lex_start()
    - mysql_reset_thd_for_next_command()
    So, initializing the lexical analyser *before* using the query cache
    is required for the cache to work properly.
    FIXME: cleanup the dependencies in the code to simplify this.
  */
  mysql_reset_thd_for_next_command(thd);
  lex_start(thd);

  thd->m_parser_state= parser_state;
  invoke_pre_parse_rewrite_plugins(thd);
  thd->m_parser_state= NULL;

  enable_digest_if_any_plugin_needs_it(thd, parser_state);

  if (query_cache.send_result_to_client(thd, thd->query()) <= 0)
  {
    LEX *lex= thd->lex;
    const char *found_semicolon;

    bool err= thd->get_stmt_da()->is_error();

    if (!err)
    {
      err= parse_sql(thd, parser_state, NULL);
      if (!err)
        err= invoke_post_parse_rewrite_plugins(thd, false);

      found_semicolon= parser_state->m_lip.found_semicolon;
    }