Bug #74569 | Description for LOCK_DATA not complete | ||
---|---|---|---|
Submitted: | 26 Oct 2014 8:59 | Modified: | 12 Nov 2014 15:24 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6.21, 5.6.22 | OS: | Any |
Assigned to: | Daniel Price | CPU Architecture: | Any |
Tags: | information_schema, innodb, innodb_locks, lock_data |
[26 Oct 2014 8:59]
Daniël van Eeden
[26 Oct 2014 8:59]
Daniël van Eeden
Added tags
[29 Oct 2014 14:34]
MySQL Verification Team
Hello Daniël, Thank you for the report. Thanks, Umesh
[29 Oct 2014 14:34]
MySQL Verification Team
// mysql> select * from information_schema.innodb_locks\G *************************** 1. row *************************** lock_id: 1805:6:3:1 lock_trx_id: 1805 lock_mode: X lock_type: RECORD lock_table: `test`.`t1` lock_index: GEN_CLUST_INDEX lock_space: 6 lock_page: 3 lock_rec: 1 lock_data: supremum pseudo-record *************************** 2. row *************************** lock_id: 1804:6:3:1 lock_trx_id: 1804 lock_mode: S lock_type: RECORD lock_table: `test`.`t1` lock_index: GEN_CLUST_INDEX lock_space: 6 lock_page: 3 lock_rec: 1 lock_data: supremum pseudo-record 2 rows in set (0.00 sec)
[12 Nov 2014 15:24]
Daniel Price
"If a gap lock is taken for key values or ranges above the largest value in the index, "LOCK_DATA" reports "supremum pseudo-record" The INNODB_LOCKS.LOCK_DATA description has been updated. The revised content should appear within the next 24 hours. http://dev.mysql.com/doc/refman/5.5/en/innodb-locks-table.html http://dev.mysql.com/doc/refman/5.6/en/innodb-locks-table.html http://dev.mysql.com/doc/refman/5.7/en/innodb-locks-table.html Thank you for the bug report.