Loading...

XML

Word

Printable

Type: Change Request
Resolution: Won't fix
Priority: Major
Fix Version/s: None
Affects Version/s: 5.0.17, 5.4.7, 6.0.0alpha6
Component/s: Server (S)
Labels:
- database

Sprint:
Sprint 82 (Nov 2021)

Steps to reproduce:

Install latest zabbix + timescaleDB 2.5.0 (currently using latest-pg12 docker tag)
Enable compression
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