[ZBX-25672] Patch from issue ZBXNEXT-9397 does not work for server with PGSQL+TimescaleDB Created: 2024 Dec 04 Updated: 2025 Jan 20 Resolved: 2025 Jan 16 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 7.0.5, 7.0.6 |
Fix Version/s: | 7.0.9rc1, 7.2.3rc1, 7.4.0alpha1 |
Type: | Problem report | Priority: | Trivial |
Reporter: | Alexis M. | Assignee: | Mihails Prihodko |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | 25h | ||
Original Estimate: | Not Specified | ||
Environment: |
Debian 12, zabbix-server-pgsql v7.0.6, PGSQL 16.5, TimescaleDB 2.17.2 |
Attachments: |
![]() |
||||||||
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | S25-W2/3 | ||||||||
Story Points: | 1 |
Description |
Steps to reproduce:
This was reported and fixed in this issue : https://support.zabbix.com/browse/ZBXNEXT-9397 From v7.0.5, the fix work like a charm for MariaDB and PGSQL database engine, but not with PGSQL+TimescaleDB.
I can't find what i'm doing wrong so i guess it's a bug ? |
Comments |
Comment by Alexander Vladishev [ 2024 Dec 05 ] |
I confirm this issue. In the case of TimescaleDB, data is sent from the "config" table even though there are no visible changes in it. This occurs at the frequency of the configuration cache updates (CacheUpdateFrequency parameter). |
Comment by Mihails Prihodko [ 2025 Jan 15 ] |
Available in versions:
|