[ZBXNEXT-7068] Compression doesn't work with TimescaleDB 2.5.0 Created: 2021 Nov 16  Updated: 2024 Apr 10  Resolved: 2021 Nov 24

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 5.0.17, 5.4.7, 6.0.0alpha6
Fix Version/s: None

Type: Change Request Priority: Major
Reporter: Eduardo Speroni Assignee: Artjoms Rimdjonoks
Resolution: Won't fix Votes: 0
Labels: database
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2021-11-24 145837.png     PNG File Screenshot 2021-11-24 145909.png    
Issue Links:
Causes
Sub-task
depends on ZBX-20251 Zabbix 5.0.11 doesn't work with Postg... Closed
Team: Team C
Sprint: Sprint 82 (Nov 2021)

 Description   

Steps to reproduce:

  1. Install latest zabbix + timescaleDB 2.5.0 (currently using latest-pg12 docker tag)
  2. Enable compression
  3. Check postgresql logs when compression runs

Result:

Compression will not work and this will be outputted to the postgres logs

2021-10-29 18:14:27.247 UTC [10576] LOG: job 1012 threw an error
2021-10-29 18:14:27.247 UTC [10576] ERROR: invalid time argument type "bigint"
2021-10-29 18:14:27.247 UTC [10576] HINT: Try casting the argument to "integer".
2021-10-29 18:14:27.247 UTC [10576] CONTEXT: PL/pgSQL function _timescaledb_internal.policy_compression_integer(i nteger,integer,bigint,integer,boolean,boolean) line 17 at FOR over SELECT rows
SQL statement "CALL _timescaledb_internal.policy_compression_integer(
job_id, htid, lag_integer,
maxchunks, verbose_log, recompress_enabled )"
PL/pgSQL function _timescaledb_internal.policy_compression(integer,j sonb) line 62 at CALL
2021-10-29 18:14:27.249 UTC [1] LOG: background worker "Compression Policy [1012]" (PID 10576) exited with exit code 1
 

Discussion thread: https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/433898-timescaledb-compression-error-invalid-time-argument-type-bigint#post434976

Expected:

Compression shouldn't throw errors

 Comments   
Comment by Artjoms Rimdjonoks [ 2021 Nov 23 ]

This is not a bug (at least in Zabbix),
The latest TimescaleDB version that is supported is 2.3 (for Zabbix 6.0):
https://www.zabbix.com/documentation/6.0/manual/installation/requirements

TimescaleDB for PostgreSQL	2.0.1-2.3	Required if TimescaleDB is used as Zabbix backend database. Make sure to install the distribution of TimescaleDB with the compression supported.

For Zabbix 5.4 it is TimescaleDB 2.1

Changing the status of this ticket to feature request (ZBXNEXT).

Comment by Artjoms Rimdjonoks [ 2021 Nov 24 ]

This seems to be a known bug in TimescaleDB that should be already fixed in the latest TimescaleDB master branch version.

Generated at Thu Apr 03 06:59:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.