Hello all;
We have Zabbix 2.2.1 with postgresql 9. 324 hosts, 8651 items and 4850 triggers are in our zabbix.
Also we have housekeeper that run every hour.
But our /opt disk size, in other word history* table size is constantly raising.
One month ago...
2 results in 0.0045 seconds.
-
PostgreSQL table definition: history_uint*
Hello. Is there a reason why PostgreSQL uses NUMERIC(20,0) instead of BIGINT for it's history_uint? BIGINT is always 8 bytes on disk, whereas NUMERIC is "two bytes for each group of four decimal digits, plus three to eight bytes overhead," per the documentation[1].
I realize...Last edited by seanc; 22-07-2012, 23:56.
