-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: after insert transaction, truncate table not wait lock release #14633
Comments
create table t1(a int); // table without pk, can not lock |
正常处理 |
暂无进度 |
11 similar comments
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
7 similar comments
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
11 similar comments
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
暂无进度 |
@iamlinjunhong 这个目前什么进展? |
已知问题,正在处理 |
正在处理 |
符合预期, 事务隔离级别为 rc,事务 a insert 1,实际上在 事务a 提交之前 事务b是看不到的,所以 truncate 不需要等待。 |
感觉这个本质是 truncate 是否是DDL类语句的问题。 如果是 delete from t1的语义,那么新insert的本来就看不到,不需要锁等待。 感觉可以让田博士和高老师看看 |
需确实是否修改该行为 |
note: 当做 drop table 等同加锁。 |
Is there an existing issue for the same bug?
Branch Name
main
Commit ID
90ee283
Other Environment Information
Actual Behavior
mo :
but mysql rr and rc isolation ,truncate table wait lock release
Expected Behavior
No response
Steps to Reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: