TimescaleDB installation for existing installation, disk size not reduced

[[email protected]]

Hello,

I installed TimescaleDB for existing PostgreSQL DB for better performance and to reduce disk size for Zabbix. Before I started I had 175GB of space for database. I installed TimescaleDB with manual it was ok, but after executing this command:

# cat /usr/share/zabbix-sql-scripts/postgresql/timescaledb.sql | sudo -u zabbix psql zabbix

it fills whole disk space after one hour to 250GB and crashed. So I increased disk size to 600GB and execute it again, during migration disk size increased to 350GB and then go down to 200GB. After that I started zabbix server and php services. After one day DB size is 205GB... What to do now? Why is the space bigger than before? Can anyone help me to troubleshoot this?
I am using Zabbix version: 6.4.13 and PostgreSQL 15.6.

Thank you,

Marek

[cyber]

Timescale alone does not give you any size reduction, it allows you to easily manage partitions.
Size reduction comes after you have enabled compression. It is there under housekeeper settings.. Administration->general->housekeeping...

There was presentation in last year Zabbix summit about implementing Timescale on already existing installation ... https://www.zabbix.com/events/zabbix...nda#day2_17:15

[[email protected]]

cyber I have compression enabled, it was enabled by default. Look at the housekeeping.png.

[cyber]

Based on that pic I would say, your db growth was normal. You reached the point where housekeeper keeps your DB in shape. If you do not add much items/hosts it will keep that size. For a month it has been quite stable and that sawtooth there probably shows timescale dropping older data, I have quite similar sawtooth on my instance.

[[email protected]]

cyber ok, but 16.4. i implemented TimescalDB and DB size is bigger from this date. It should be much more less, right? Why not?

[cyber]

Beats me.. All I can say is "something is wrong.. :P ". I don't think I am enough of a specialist here to tell you to check here and there or run some queries..
When I switched compression on, my DB size dropped from ~1.2T to some 5-600-ish G....