[MDEV-29128] Possible table (mysql.innodb_table_stats) structure mismatch in internals Created: 2020-02-10 Updated: 2023-09-19 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 10.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Sergii Gulyk | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Running mariadb as a service on Windows machine (7-10, also server versions) |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
We have got datafiles folder from the customer, so I have no steps for reproducing this situation. However, let's assume that we want to get out of it somehow. Please see results of two queries in the attachment. I would like to highlight difference in
from information_schema.columns
Somehow we managed to have column length updated in information_schema.columns (597 bytes length), but not in information_schema.innodb_sys_columns (192 bytes length). mysql_upgrade reports that mysql.innodb_table_stats as well as mysql.innodb_index_stats are up to date, while customer continue getting
last_update type is also wrong, you can see it the attached file, but it is not that obvious as string length difference. I've prepared archive of the internals, but it is 75Mb and I cannot attach it here. |
| Comments |
| Comment by Sergii Gulyk [ 2020-02-10 ] |
|
Reproduces on 10.3.12 and latest built from sources 10.3.21 |
| Comment by Roman [ 2020-03-06 ] |
|
Greetings, |
| Comment by Sergii Gulyk [ 2020-03-06 ] |
|
Hi Roman, No, I definitely did not want to. Could you please move the issue where appropriate? |
| Comment by Roman [ 2022-07-18 ] |
|
danblack Could you plz move this issue back to the MDEV queue? |