| Bug #95598 | performance_shema.data_locks shows incorrect lock information | ||
|---|---|---|---|
| Submitted: | 2 Jun 2019 11:10 | Modified: | 7 Jun 2019 15:02 |
| Reporter: | Young Chen | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Performance Schema | Severity: | S3 (Non-critical) |
| Version: | 8.0.12 | OS: | CentOS (CentOS release 6.5 (Final)) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | data_locks, insert on duplicate key update | ||
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
[4 Jun 2019 15:14]
Young Chen
[7 Jun 2019 13:56]
Young Chen
This picture is what record-lock shows, please refer to : https://dev.mysql.com/doc/refman/8.0/en/innodb-locking.html
Attachment: record_lock.png (image/png, text), 230.69 KiB.
[7 Jun 2019 13:57]
Young Chen
This screen shot is what next-key lock shows, please refer to :https://dev.mysql.com/doc/refman/8.0/en/innodb-locking.html
Attachment: next_key_lock.png (image/png, text), 247.20 KiB.
