Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Won't Do
-
1.4.3
-
None
-
2020-5, 2020-6, 2020-7
Description
*strong text*After integration, INSERT SELECT is no longer using "vtable" like method for executing SELECT part (does it via ROW interface). The fix is to push SELECT into Select Handler (a 1.4 replacement of vtable).
As of 1.4.3 MCS uses table API to query the data running INSERT..SELECT. Mentioned ENT-669 backports 10.5 feature described by CLX-77 into 10.4 Ent. The feature enables Select Handler to execute the query part.
1.4 forces MCS to skip OFFSET processing b/c MDB applies OFFSET on its own.
1.5 contains changes that allows to push OFFSET down to a smart engine.
Attachments
Issue Links
- duplicates
-
MCOL-545 Bulk operation produce IO on UM
- Closed
- relates to
-
MCOL-3929 SELECT INTO..OUTFILE
- Closed
-
MDEV-16327 Server doesn't account for engines that supports OFFSET on their own.
- Closed
-
MDEV-18553 Make LIMIT/OFFSET processing uniform
- Closed