Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
Goal
Add support for WITH VALIDATION | WITHOUT VALIDATION to
ALTER TABLE ... EXCHANGE PARTITION ... WITH TABLE
WITH VALIDATION should be the default behavior.
Must also cover CONVERT {TABLE|PARTITION} TO
Background
When WITHOUT VALIDATION is specified, there is no check that all rows in the added table fulfills the partition restrictions. If there is inconsistencies, it will result in rows later not being found in SELECT, UPDATE or DELETE.
MySQL has had this since 5.7.5 and it's important when adding big tables to a partitioned table to avoid the expensive row-by-row check.
h3. Supplemental feature
Make THAN keyword optional in partition definition of range partitioning.
Attachments
Issue Links
- causes
-
MDEV-33125 CHECK TABLE does not recognize corruption after EXCHANGE WITHOUT VALIDATION on system-time partitioning
- Closed
-
MDEV-33128 WITHOUT VALIDATION allows to insert duplicate values into unique key without a way to repair
- Open
- is part of
-
MDEV-22162 Make partitions more flexible to use
- Open
- relates to
-
MDEV-20498 Assertion `table_share->tmp_table != NO_TMP_TABLE || m_lock_type == 1' failed upon REBUILD PARTITION
- In Progress
-
MDEV-22165 CONVERT TABLE: move in partition from existing table
- Closed
-
MDEV-22166 CONVERT PARTITION: move out partition into a table
- Closed
-
MDEV-28298 Add Foreign key to a table instantly without checking existing data
- Open
-
MDEV-33190 Errors or assertion failure upon REPAIR on partitioned Aria table with misplaced rows
- Open