Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
11.6.0
-
None
Description
Information_schema.slave_status, added in MDEV-33856, cuts off strings way too short, whereas SHOW SLAVE STATUS does not. See the following example with Last_error:
Information_schema.slave_status cuts off the error quite badly
MariaDB [(none)]> select Last_SQL_Error,Last_SQL_Errno from information_schema.slave_status\G
|
*************************** 1. row ***************************
|
Last_SQL_Error: Error 'Duplicate ent
|
Last_SQL_Errno: 1062
|
Whereas SHOW SLAVE STATUS writes the full error output:
MariaDB [(none)]> show slave status\G
|
*************************** 1. row ***************************
|
...
|
Last_SQL_Errno: 1062
|
Last_SQL_Error: Error 'Duplicate entry '1' for key 'PRIMARY'' on query. Default database: ''. Query: 'insert into test.t1 values (1)'
|
It seems the field lengths that are set for SHOW SLAVE STATUS are not actually respected in its output, and when using those values for INFORMATION_SCHEMA.SLAVE_STATUS, they are much too short.
Attachments
Issue Links
- is caused by
-
MDEV-33856 Alternative Replication Lag Representation via Received/Executed Master Binlog Event Timestamps
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is caused by |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 11.6.0 [ 29839 ] | |
| Fix Version/s | 11.6 [ 29515 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
Fixed in latest commit for
MDEV-33856