executor: make projection executor unparallel for insert/update/delete (#30290)

[ti-srebot]

cherry-pick #30290 to release-5.2
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/30387

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/30387:release-5.2-4fbbd5a77df2

---

What problem does this PR solve?

Issue Number: close #26832

Problem Summary:

The memdb is not thread-safe, and that's the root cause of issue 26832

What is changed and how it works?

In insert/update/delete statement, do not use the parallel projection, choose the unparallel one intead.

This can avoid the concurrent visit of the memdb in issue 26832.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

I try to add some unit test code like this and run it with -race flag, but can't reproduce.

+func (s *testSuite8) TestIssues26832DataRace(c *C) {
+       tk := testkit.NewTestKit(c, s.store)
+       tk.MustExec("use test")
+       tk.MustExec("drop table if exists t")
+       tk.MustExec("create table t (a int unique)")
+       tk.MustExec(`CREATE TABLE IF NOT EXISTS order_line (
+               ol_o_id INT NOT NULL,
+               ol_d_id INT NOT NULL,
+               ol_w_id INT NOT NULL,
+               ol_i_id INT NOT NULL,
+               ol_delivery_d INT,
+               PRIMARY KEY(ol_w_id, ol_d_id, ol_o_id)) partition by hash(ol_w_id) partitions 10`)
+       for i:=0; i<1000; i++ {
+               tk.MustExec("insert into order_line value (?, ?, ?, ?, ?)", i, i, i, i, i)
+       }
+
+       for i:=0; i<1000; i++ {
+               v := rand.Intn(1000)
+               tk.MustExec(`UPDATE order_line SET ol_delivery_d = ol_delivery_d + 1 WHERE (ol_w_id, ol_d_id, ol_o_id) IN (
+       (?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?))`,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v,
+                       v,v,v)
+       }
+}

and then, I try the TPCC on my local machine, and with no luck ... it doesn't reproduce

tiup bench tpcc --warehouses 10 --parts 10 prepare -T 16 -D bench
tiup bench tpcc --warehouses 10 --parts 10 run -T 16 -D bench

This change is simple enough, so maybe we can merge it first and see whether it reproduce in the future.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

It should not impact the write performance in most cases, because the insert/update/delete is unparalleled
and be the bottleneck, the change of projection does't change this fact.

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@tiancaiamao you're already a collaborator in bot's repo.

[tiancaiamao]

/run-check_dev

[VelocityLight]

This pull request is closed because it's related version has closed automatic cherry-picking.
If it's still needed, you can reopen it or just regenerate it using bot,
see:

• https://prow.tidb.io/command-help#cherrypick
• https://book.prow.tidb.net/#/plugins/cherrypicker

You can find more details at:

• https://internals.tidb.io/t/topic/785