Zabbix PostgreSQL: TimeScaleDB vs Partitioning by clock

[jurassoff]

Hello!
The question is about history* tables.

I want to increase DB performance with Zabbix v6 on PostgreSQL v15 by partitioning history* tables. The planned partitioning key is "clock".

TimeScaleDB is undesirable due to some internal issues, but it can be overcome.

Please explain if there are some issues/problems using PostgreSQL Partitioning by "clock" key instead of TimeScaleDB.

Thanks in advance.

[cyber]

IIRC any mysql/mariadb partitioning goes by that anyway, so if you cannot use TS, it should be OK to partition it by "clock"... Of course, you need to make sure partitions exist and are removed as needed...