Skip to content

Non-transactional DML statement is interrupted by max_execution_time #64282

Description

@pcqz7

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> set max_execution_time=5000;
Query OK, 0 rows affected (0.00 sec)

mysql> batch on id limit 200 update sbtest1 set k=1 where k is not null;
ERROR 1105 (HY000): context canceled

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

The max_execution_time only affects read-only query.

3. What did you see instead (Required)

The non-transactional DML statement is affected by the variable.

4. What is your TiDB version? (Required)

v8.5.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects-6.5This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.report/customerCustomers have encountered this bug.severity/majorsig/executionSIG executiontype/bugThe issue is confirmed as a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions