The schema is: CREATE TABLE vm_action_info(
POSTGRES DEADLOCK UPDATE
Process 31876: update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 where id=$2 Process 31876 waits for ShareLock on transaction 4228275 blocked by process 31530. 11:00:25 IDT DETAIL: Process 31530 waits for ExclusiveLock on tuple (0,68) of relation 70337 of database 69205 blocked by process 31876. 11:00:25 IDT STATEMENT: update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 where id=$2 11:00:25 IDT HINT: See server log for query details.
Process 31530: update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 where id=$2 Process 31533: update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 where id=$2 Process 31530 waits for ExclusiveLock on tuple (0,68) of relation 70337 of database 69205 blocked by process 31533. 11:00:25 IDT DETAIL: Process 31533 waits for ShareLock on transaction 4228275 blocked by process 31530.
11:00:24 IDT STATEMENT: update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 where id=$2 The error that I'm getting in the log 11:00:24 IDT HINT: See server log for query details. How does two identical simple updates can deadlock each other ? Update public.vm_action_info set last_on_demand_task_id=$1, version=version+1 I'm working with postgres 9.1 and getting deadlock exception under excessive execution of a simple update method.Īccording to the logs the deadlock occurs due to execution of two identical updates at the same time.
0 kommentar(er)
