| Bug #121061 | InnoDB wrong result for a full-column secondary index on an externally stored field during MVCC lookup | ||
|---|---|---|---|
| Submitted: | 6 Aug 8:37 | ||
| Reporter: | Xu Leo | Email Updates: | |
| Status: | Open | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 8.0.46 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | external field, innodb, MVCC, secondary index, wrong result | ||
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[6 Aug 8:38]
Xu Leo
[6 Aug 8:39]
Xu Leo
reporduce testcase
Attachment: full_column_external_sec_index.test (application/octet-stream, text), 2.31 KiB.
[6 Aug 8:39]
Xu Leo
reporduce testcase result
Attachment: full_column_external_sec_index.result (application/octet-stream, text), 1.83 KiB.
