Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
As hinted in MDEV-21602, CREATE TABLE...SELECT is currently implemented in multiple transactions:
- Transaction(s) to create (each partition or subpartition of) the table
- Another transaction to execute INSERT...SELECT
- If an error occurs: transaction(s) to execute handler::delete_table()
A cleaner solution would be to use a single transaction for the entire operation. If an error occurs, we would simply roll back the operation.
Attachments
Issue Links
- blocks
-
MDEV-4259 transactional DDL
- Open
-
MDEV-11655 Transactional data dictionary
- Open
- includes
-
MDEV-25292 Atomic CREATE OR REPLACE TABLE
- Stalled
- is blocked by
-
MDEV-25919 InnoDB reports misleading lock wait timeout on DDL operations
- Closed
- relates to
-
MDEV-21602 CREATE TABLE…PRIMARY KEY…SELECT workaround causes DROP TABLE to ignore locks
- Closed