We are observing locking problems related to Zabbix and concurrent transactions updating the same database record in Postgresql. Is there anyway that you can eliminate these errors on the items table. Is there any kind of facility that can hand lock contention in Zabbix?
29715:20120921:092808.185 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: deadlock detected
DETAIL: Process 29766 waits for ShareLock on transaction 16116280; blocked by process 29770.
Process 29770 waits for ShareLock on transaction 16116271; blocked by process 29772.
Process 29772 waits for ShareLock on transaction 16116298; blocked by process 29766.
HINT: See server log for query details.
[update items set lastclock=1348244871,lastns=231075443,prevorgvalue ='0',prevvalue=lastvalue,lastvalue='0' where itemid=23331;
29715:20120921:092808.185 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: deadlock detected
DETAIL: Process 29766 waits for ShareLock on transaction 16116280; blocked by process 29770.
Process 29770 waits for ShareLock on transaction 16116271; blocked by process 29772.
Process 29772 waits for ShareLock on transaction 16116298; blocked by process 29766.
HINT: See server log for query details.
[update items set lastclock=1348244871,lastns=231075443,prevorgvalue ='0',prevvalue=lastvalue,lastvalue='0' where itemid=23331;