session, com_stmt: store and restore the params for cursor fetch (#41441)

[ti-chi-bot]

This is an automated cherry-pick of #41441

What problem does this PR solve?

Issue Number: close #40094

Problem Summary:

TiDB cannot handle concurrently running statements. This PR stores and restores the params.

What is changed and how it works?

Store and restore the prepared params in session

Check List

Tests

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

The following JDBC codes run without panic:

import java.sql.*;

public class Example {
    public static void main(String[] args) throws SQLException, InterruptedException {
        Connection conn = DriverManager.getConnection("jdbc:mysql://127.0.0.1:4000/test?useCursorFetch=true&useServerPrepStmts=true&useSSL=false", "root", "");

        conn.setAutoCommit(false); // must set

        conn.prepareStatement("drop table if exists t").execute();
        conn.prepareStatement("create table t (id int auto_increment primary key, id_2 int)").execute();
        conn.prepareStatement("insert into t values (1,1)").execute();
        conn.prepareStatement("insert into t values (2,2)").execute();

        // submit a statement with more arguments:
        PreparedStatement statement1 = conn.prepareStatement("" +
                "select * " +
                "from " +
                "t " +
                "where id = ? and id_2 = ?");
        statement1.setFetchSize(500);
        statement1.setInt(1, 1);
        statement1.setInt(2, 2);
        ResultSet rs_1 = statement1.executeQuery();

        // submit a statement with less arguments:
        PreparedStatement statement2 = conn.prepareStatement("" +
                "select * " +
                "from " +
                "t " +
                "where (id = ?)");
        statement2.setFetchSize(500);
        statement2.setInt(1, 1);
        ResultSet rs_2 = statement2.executeQuery();

        // fetch the result from the first argument
        while (rs_1.next()) {
            int result = rs_1.getInt(1);

            System.out.println(result);
        }
        while (rs_2.next()) {
            int result = rs_2.getInt(1);

            System.out.println(result);
        }

        statement1.close();
        statement2.close();
        conn.commit();
        conn.close();

    }
}

Release note

Fix the issue that the prepared params are lost while executing another statement between EXECUTE and FETCH command.

[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-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev_2	1803352	link	true	/test check-dev2
idc-jenkins-ci-tidb/unit-test	1803352	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev	1803352	link	true	/test check-dev
idc-jenkins-ci-tidb/build	1803352	link	true	/test build
idc-jenkins-ci-tidb/mysql-test	1803352	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[YangKeao]

I'll cherry-pick #42473 to 6.1 and 6.5, so close this one.