-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
executor: point get for update read panic on partition table #25528
Comments
/cc @qw4990 |
@tiancaiamao it seems this issue is caused by -2 ID introduced by #21148, PTAL |
Oh, I get the point ... I add a extra partition table ID column for select lock, the table reader executor will add the extra column and pass the extra column to the ancestral select lock executor. However, I forget the point get / batch point get cases for that extra PID column. |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
It is introduced by another bugfix PR, and it's fixed immediately, so I just change the |
DROP TABLE IF EXISTS `t2`;
CREATE TABLE `t2` ( `c1` int(11) NOT NULL, `c2` int(11) DEFAULT NULL, `c3` int(11) DEFAULT NULL, `c4` int(11) DEFAULT NULL, PRIMARY KEY (`c1`) /*T![clustered_index] CLUSTERED */, KEY `k2` (`c2`), KEY `k3` (`c3`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin PARTITION BY HASH( `c1` ) PARTITIONS 10;
INSERT INTO t2 (`c1`, `c2`, `c3`, `c4`) VALUES (1, 1, 1, 1) , (3, 3, 3, 3) , (2, 2, 2, 2) , (4, 4, 4, 4);
select * from t2 where c1 in (3, 4) order by c2 for update;
Still got panicked. @tiancaiamao PTAL |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
fail in test-store
2. What did you expect to see? (Required)
success with results
3. What did you see instead (Required)
Error 1105: runtime error: invalid memory address or nil pointer dereference
the panic stack
Seems the point get executor decodes value with incorrect colunm index or offset.
The
non for update point get read
andnon-partition for update point get read
are ok.4. What is your TiDB version? (Required)
master ed686d1
release-5.1 4ca5d03
The text was updated successfully, but these errors were encountered: