Hello!
We've deployed Zabbix 6.0.14 server on PostgreSQL 15.7 for a test. The data was logicaly replicated from DB under Zabbix 5.0.22. The 'history*' tables were not replicated. Primary Keys were constructed as per instructions for upgrade (history_pkey is on 'itemid' + 'clock' + 'ns' columns).
2024-09-25 14:15 GMT we received a pack of errors in PostgreSQL log like 'duplicate key value violates unique constraint "history_pkey"'. One of corresponding values have clock 1727330789, that is "Thu Sep 26 2024 06:06:29 GMT". Looks like a mesage from future. And the row in history table really exists.
The question is how could Zabbix Server insert such a row into history table subsequently trying to duplicate it since Zabbix 6 version starts using PK-constraint on history* tables?
Thanks in advance.
We've deployed Zabbix 6.0.14 server on PostgreSQL 15.7 for a test. The data was logicaly replicated from DB under Zabbix 5.0.22. The 'history*' tables were not replicated. Primary Keys were constructed as per instructions for upgrade (history_pkey is on 'itemid' + 'clock' + 'ns' columns).
2024-09-25 14:15 GMT we received a pack of errors in PostgreSQL log like 'duplicate key value violates unique constraint "history_pkey"'. One of corresponding values have clock 1727330789, that is "Thu Sep 26 2024 06:06:29 GMT". Looks like a mesage from future. And the row in history table really exists.
The question is how could Zabbix Server insert such a row into history table subsequently trying to duplicate it since Zabbix 6 version starts using PK-constraint on history* tables?
Thanks in advance.