Skip to content

max_execution_time should only take affect on select sql #64360

@windtalker

Description

@windtalker

Bug Report

Please answer these questions before submitting your issue. Thanks!
According to mysql's doc, max_execution_time only works for select sql, in TiDB, it try to align this behavior, however, there is still some corner cases which max_execution_time affect non select sql, for example, in #56923, it tries to set context's timeout using max_execution_time, so rpc can be aware of max_execution_time, but it actually does not check InSelectStmt, which means a non select sql will be affected by this pr.

1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions