Zabbix 1.4.4

Seems I had problems with system clock and zabbix got some very big value (negative?) so postgres rejected this insert and server died. Some action to prevent server death and reporting of this sort of issues would be great.

526:20080217:040605 Query::insert into history_uint (clock,itemid,value) values (1203203165,19565,18446744073709551614)
526:20080217:040605 Query failed:PGRES_FATAL_ERROR:ERROR: bigint out of range

526:20080217:040605 Query::select num,value_min,value_avg,value_max from trends where itemid=19565 and clock=1203202800
526:20080217:040605 Query failed:PGRES_FATAL_ERROR:ERROR: current transaction is aborted, commands ignored until end of transaction block

502:20080217:040605 One child process died. Exiting ...
502:20080217:040607 ZABBIX Server stopped