Changed Semantic of Multiple Tables RENAME to Avoid Possible Deadlocks

Why it matters

This feature addresses issues with deadlocks that could occur when using RENAME on multiple tables simultaneously. By modifying the semantics of these operations, it ensures safer schema changes and improves the reliability of database migrations and maintenance tasks.

How to use it

Users will benefit from this change automatically when executing RENAME statements involving multiple tables, as the new implementation handles locking internally to avoid deadlocks. No additional configuration is required.