Debian v12.8, TimescaleDB v2.17.2, Postgresql v16.6, Zabbix 7.0.6.

TimescaleDB 2.18.0 has not been released yet. Once it becomes available, we will add support for this version in Zabbix.

As written in the first link https://github.com/timescale/timescaledb/issues/7410 problem is due to TimescaleDB internal bug. The fix is going to be released in TimescaleDB version 2.18.
Meanwhile setting timescaledb.enable_vectorized_aggregation = off can be used as workaround.

What askolmeisters writes, is right. I also implemented this at some installations for clients using PostgreSQL 16 together with TimescaleDB 2.17.x..

We'll just have to wait for TimescaleDB 2.18 and in the meanwhile have the setting timescaledb.enable_vectorized_aggregation = off  set in the postgresql-config file (don't forget to restart PostgreSQL for this to become active!).

For the dutch speaking Zabbix users I wrote a little article on this to help them: https://www.xifeo.nl/zabbix/blog/problemen-zabbix-grafieken-met-timescaledb-2-17-x/

I can confirm that adding timescaledb.enable_vectorized_aggregation = off in the prostgresql configuration file fixes the issue, also you do not need to restart the postgresql service a simple reload of the configuration using SELECT pg_reload_conf(); will suffice.

Today i upgraded zabbix-server to 7.0.10  and timescaledb to 2.18.2 and problem still exist

I have the same problem

Based on user comments, I am reopening this issue for further investigation.

Thanks

FYI
Zabbix added support for Timescaledb 2.18 in ZBXNEXT-9771 in versions:
pre-6.0.39rc1
pre-7.0.10rc1
pre-7.2.4rc1
pre-7.4.0alpha1

today I tried to open the charts for the last 30 days again
I don't see any problems. although they were. see my screenshot above.
but if I switch charts for the last 3 months or older - I get errors

Guys, just letting you know, in my case, I managed to resolve it by upgrading the TimescaleDB extension to 2.18.2, and even before that, I had initiated reindexing, like ChatGPT informed me.

REINDEX TABLE history;
REINDEX TABLE trends;
ANALYZE history;
ANALYZE trends; 

Don't know if it was necessary, but now it works like expected.

Do this commands on already upgraded to 2.18.2 installation. Not worked for me.

Also notice errors on 30-day history again. 

Try to get problem date.

from now-13d - no errors

from now-14d - errors

I recently upgraded to TimescaleDB 2.19 (and have PostgreSQL 16). I resetted the"timescaledb.enable_vectorized_aggregation" to the default and restarted PostgreSQL. 
Everything works for me right now, so it looks like the 2.19 TimescaleDB version fixes this issue finally!

Upgrading TimescaleDB to 2.19 not work for me. Problem still exist.

Did you also update the extension in the database itself?

I did full apt-get update && apt-get dist-upgrade and restarted the server.

No, that doesn't do the trick.

First shutdown zabbix-server (to be safe and sure)
You have to logon as postgresql-user:
`psql -X zabbix`

zabbix=# \dx

(check which extension is used)

zabbxix=# quit

connect again (psql -X zabbix)
zabbix=# ALTER EXTENSION timescaledb UPDATE;

Then you can check the version and it should state something like this:

{{                                                List of installed extensions
    Name     | Version |   Schema   |                                      Description                                      
-----------------------------+--------------------------------------------------------------------------------------
 plpgsql     | 1.0     | pg_catalog | PL/pgSQL procedural language
 timescaledb | 2.19.0  | public     | Enables scalable inserts and complex queries for time-series data (Community Edition)
(2 rows)
}}

Many thanks, Raimond.

I rolled back a snapshot Zabbix VM from yesterday test upgrade to 2.19

Despite the installed TimescaleDB version is 2.18.2

\dx shows:

    Name     | Version |   Schema   |

------------------------------+

 plpgsql     | 1.0     | pg_catalog |

 timescaledb | 2.17.2  | public     |

after i execute command  

ALTER EXTENSION timescaledb UPDATE;

\dx shows 2.18.2 and problem is gone.

I'll stay on 2.18.2 as supported version for now.

Great that it worked! That's a step which people forget to do quite a lot. The binaries are upgraded, but your extension in the database has to be done manually .

upgrading timescaledb extension from 2.17 to 2.18.2 fixed the problem also for me on Postgres 17

Hi Same as above. After upgrading to 2.18.2 on my PG 17 instance, everything is back to normal. Thanks for your help !