In moving up to version 5 of zabbix I'm in process of planning a migration from an old version 9 of postgres (using trigger based date partitioning on history and trend tables) on an old server to the current stable version 13 on a new database server. I've been trying to work out performance wise if it's better to use the native partitioning or use timescaledb. I've seen some reports that on 12 and 13 there is very little performance difference in it and if we're not keeping a massive amount of history then the advantages of compression are minimal.
Is there anything else I've missed that would mean that timescaledb offers other benefits that I won't get without it?
Is there anything else I've missed that would mean that timescaledb offers other benefits that I won't get without it?
...
Comment