Bug 460172 - Very frequent SQL errors dumped in .local/share/akonadi/db_data/mysql.err
Summary: Very frequent SQL errors dumped in .local/share/akonadi/db_data/mysql.err
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.21.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-09 17:16 UTC by flyos
Modified: 2022-10-25 14:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flyos 2022-10-09 17:16:43 UTC
SUMMARY
Since a few days (sorry, can't be more precise), Akonadi started filling the SQL error log with the following every few minutes (lots of error each time, but repeat of those exact two lines) :
[ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
[ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
I first noticed the issue because my hard drive was full, and mysql.err.old was several Gb large!

STEPS TO REPRODUCE
I don't know how to reproduce, sorry, but the behaviour is the same on two computers of mine, both installed with openSUSE Tumbleweed, up-to-date, and both with Akonadi accounts (several IMAP, CalDAV, CardDAV).

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20221006
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.10-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz
Memory: 15.6 Gio of RAM
Graphics Processor: AMD CAICOS
Comment 1 flyos 2022-10-10 07:42:10 UTC
Using a third computer (on which I can confirm the bug, same setting), I can pinpoint the date of the bug September 14th, although it doesn't help finding a version change or the such, I guess it's still a ballpark estimation of how "old" is the bug.