Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.31, 10.3.22, 10.4.12
-
None
Description
In SHOW ENGINE INNODB STATUS output or in the output of the lock monitor, the query text and other basic information about the session seems to get copied to a buffer that is only 1024 bytes large. See here:
https://github.com/MariaDB/server/blob/mariadb-10.2.31/storage/innobase/handler/ha_innodb.cc#L2155
This means that even moderately long queries can be truncated.
Maybe we should increase the size of this buffer.
Attachments
Issue Links
- relates to
-
MDEV-17237 thread IDs are printed in different formats in different sections of SHOW ENGINE INNODB STATUS output
- Open
-
MDEV-17238 Document special thread IDs used in SHOW ENGINE INNODB STATUS output
- Open
-
MDEV-18391 Print ENGINE INNODB STATUS in machine parsable format
- Open
-
MDEV-18429 Consistent non-locking reads do not appear in TRANSACTIONS section of SHOW ENGINE INNODB STATUS
- Closed
-
MDEV-18572 Thread executing DROP TABLE listed twice in SHOW ENGINE INNODB STATUS output
- Open
-
MDEV-18582 Port status variables related to SHOW ENGINE INNODB STATUS from XtraDB to InnoDB in 10.2+
- Closed
-
MDEV-18698 Show InnoDB's internal background threads in SHOW ENGINE INNODB STATUS
- Open
-
MDEV-21330 Lock monitor doesn't print a semaphore's last reserved thread in non-debug builds and INFORMATION_SCHEMA.INNODB_SYS_SEMAPHORE_WAITS is totally broken
- Closed
-
MDEV-21390 lock_print_info_summary() should work even when trx_sys.mutex is locked
- Closed
-
MDEV-21566 Lock monitor doesn't print a name for RW-latches
- Closed