Atomic CREATE OR REPLACE TABLE (MDEV-25292)

[MDEV-28753] Review InnoDB changes for MDEV-25292 Created: 2022-06-06  Updated: 2022-06-21  Resolved: 2022-06-21

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: None
Fix Version/s: N/A

Type: Technical task Priority: Critical
Reporter: Aleksey Midenkov Assignee: Marko Mäkelä
Resolution: Done Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-25292 Atomic CREATE OR REPLACE TABLE Stalled

 Description   

"InnoDB changes" article has been added to the main task commit.

Any of the branches can be reviewed:
bb-10.7-midenok-MDEV-25292
preview-10.10-MDEV-25292-atomic-cor



 Comments   
Comment by Marko Mäkelä [ 2022-06-13 ]

I think that the design questions and suggestions in MDEV-25292 must be addressed before this can be reviewed.

Comment by Marko Mäkelä [ 2022-06-21 ]

I "reviewed" the changes by submitting my own versions of the InnoDB changes. There was apparently no need to remove the assertion ut_ad(err != DB_DUPLICATE_KEY) from row_rename_table_for_mysql().

Generated at Thu Feb 08 10:03:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.