Bug #108864 Contribution: New \'RENAME TABLE ... NO LOCK CHECK\' optional clause.
Submitted: 24 Oct 2022 20:34 Modified: 25 Oct 2022 5:44
Reporter: OCA Admin (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: DDL Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[24 Oct 2022 20:34] OCA Admin 
Description:
This bug tracks a contribution by Shlomi Noach (Github user: shlomi-noach) as described in http://github.com/mysql/mysql-server/pull/426

How to repeat:
See description

Suggested fix:
See contribution code attached
[24 Oct 2022 20:34] OCA Admin 
Contribution submitted via Github - New 'RENAME TABLE ... NO LOCK CHECK' optional clause.  
(*) Contribution by Shlomi Noach (Github shlomi-noach, mysql-server/pull/426#issuecomment-1289358706): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_1096477339.txt (text/plain), 7.81 KiB.
[25 Oct 2022 5:44] MySQL Verification Team 
Hello Shlomi,

Thank you for the report and contribution.

regards,
Umesh
[24 Apr 2023 9:16] Shlomi Noach 
I set myself a reminder for followup in 6 month. Do you believe this contribution may be accepted?
[21 Jun 2023 6:28] Shlomi Noach 
I am actually keen to make a change here: instead of modifying the SQL syntax (thus, `yacc`, `lex` and all the call stack), I would like to introduce a global/session variable such as `rename_tables_skip_lock_check` (defaults `false` for standard behavior). WDYT?