unexpected results returned by BatchPointGet

[qw4990]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table t (
    id bigint(20) unsigned,
    primary key(id)
);

insert into t values (8738875760185212610);
insert into t values (9814441339970117597);

select id from t where id in (8738875760185212610, 9814441339970117597) order by id;

2. What did you expect to see? (Required)

mysql> select id from t where id in (8738875760185212610, 9814441339970117597) order by id;
+---------------------+
| id                  |
+---------------------+
| 8738875760185212610 |
| 9814441339970117597 |
+---------------------+
2 rows in set (0.00 sec)

3. What did you see instead (Required)

mysql> select id from t where id in (8738875760185212610, 9814441339970117597) order by id;
+---------------------+
| id                  |
+---------------------+
| 9814441339970117597 |
| 8738875760185212610 |
+---------------------+
2 rows in set (0.00 sec)

4. What is your TiDB version? (Required)

mysql> select version();
+-------------------------------------------------+
| version()                                       |
+-------------------------------------------------+
| 5.7.25-TiDB-v4.0.0-beta.2-1253-g0e4b809ca-dirty |
+-------------------------------------------------+
1 row in set (0.00 sec)

[sre-bot]

Integrity check:
RCA symptom trigger_condition affect_version fix_version fields are empty
@lysu
Please comment /info to get template

[ti-srebot]

Please edit this comment to complete the following information

Bug

1. Root Cause Analysis (RCA)

after #14775, tidb support point get as a data source, so we have the chance to get init logical plan like [sort -> pointBatchGet]
#14775 also let a optimize make [sort -> pointBatchGet] to [pointBatchGet(sortable)]

but for pk is handle PointGet, old code treat handle as signed int and didn't take care situation that unsign pk is handle

2. Symptom

the result is wrong, records didn't sort as to desire

3. All Trigger Conditions

need to meet 3 conditions to trigger this bug.

• the user use unsigned int as the primary key
• primary key value is larger than maxInt64
• want point batch get and want to sort by primary key

4. Workaround (optional)

sort again in programm

5. Affected versions

[v4.0.0:v4.0.7]

6. Fixed versions

v4.0.8