-
Change Request
-
Resolution: Unresolved
-
Minor
-
None
-
S24-W42/43, S24-W44/45, S24-W46/47, S24-W48/49, S24-W50/51/52/1, S25-W2/3, S25-W4/5, S25-W6/7, S25-W8/9
-
14
DB table `config` stores everything in a single row. This poses an issue with mysql limitations on maximum row size. https://dev.mysql.com/doc/mysql-reslimits-excerpt/8.0/en/column-count-limit.html#row-size-limits
In particular:
The internal representation of a MySQL table has a maximum row size limit of 65,535 bytes, even if the storage engine is capable of supporting larger rows. BLOB and TEXT columns only contribute 9 to 12 bytes toward the row size limit because their contents are stored separately from the rest of the row.
We are reaching this limit with `config` table.
Propose to redesign the way we store data, that currently resides in `config` table, to eliminate this issue altogether.
- caused by
-
ZBXNEXT-3706 mysql utf8 vs utf8mb4
-
- Closed
-
- is duplicated by
-
ZBXNEXT-9054 Convert config table to key-value format
-
- Closed
-
- related to
-
ZBX-25707 Not possible to separate audit records for HA nodes
-
- READY TO DEVELOP
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...