Centos 7.x

On mysql "proxy_history.value" has "longtext" type, which is limited for 4GB.
So it's not a limit.

HI Oleksii,

Fantastic but why do you have so huge type  from the doc i saw this (https://www.zabbix.com/documentation/current/manual/config/items/item#text_data_limits): 

Strange?

I am agree that makes sense to add one more column to the table - "Longtext".
We don't state on the page where each column is user, right? But at least it may indicate that "Text" is not maximal one.

Hi Oleksii, 

Maybe i missed something but how we can decide what table the LLD have to use on the Proxy? 

At the moment with a fresh Zabbix 5.0 installation we still have this kind of limits, do you mention some sort of workaround?

Thanks so much

The limit comes from user parameter, not from the fact that you use proxy.

Maybe the 2nd sentence, you initially quoted, sounds more scary than it is actually, and it may mislead.
The "proxy_history.value"for:
mysql - Longtext = 4G https://dev.mysql.com/doc/refman/8.0/en/storage-requirements.html
postgres - Text = unlimited length https://www.postgresql.org/docs/9.1/datatype-character.html
sqlite3 - Text = practical default limit is 1 billion https://www.sqlite.org/limits.html
oracle - did not check.

I'd rewrite the sentence or would remove it at all.

The table lists data limits for item value types (character, log text). LLD rules (while technically stored into items table) is different matter.

I think if the returned value is related to DB type i would suggest to mention on the docs.

In our case we have installed the Zabbix Proxy DB on a Centos 7.7 with the default MariaDB 5.5.64, at the moment the table of "proxy_history" is defined like this:

so is defined as "longtext", maybe is a problem related to the MariaDB version 5.5 ?

The problem was not reproducible, so we can close the issue.