Search Postgresql Archives
deadlocks in multiple-triggers environment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: pgsql-general@xxxxxxxxxxxxxx
- Subject: deadlocks in multiple-triggers environment
- From: hubert depesz lubaczewski <depesz@xxxxxxxxx>
- Date: Wed, 8 Jun 2005 17:45:45 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=CYLHkkfIhZYKd7A65QCWwB6zA0a3G/plTW91u4Jr9wYezqvazIvucwccOF03O7hNn4wY4hPanUatji7/jjH6SO6THK/6iuQzhyXAlT6pWpwnpdTx6PbcITzBcfOBLtTNDi4l3t58bwqq1bjhgFuSOjLyXzcqc+Ckkz7QNbl21IA=
- Reply-to: hubert depesz lubaczewski <depesz@xxxxxxxxx>
- Sender: pgsql-general-owner@xxxxxxxxxxxxxx
hi
i have a stituation a situation where i have multiple tables, and multiple triggers on all of them.
at least 1 or 2 triggers on at lease 4 different tables does updates to main cache table.
now.
i have tasks which involve simultaneously (from different machines even) modifying all of the "source" tables.
and i get some deadlocks.
what is the best way to fight deadlocks?
how to find exactly what happened deadlock - which command, which trigger, which function?
how to avoid them (deadlocks).
i can't lock all tables for update, because they happen constantly.
any clues?
pointers? urls?
depesz
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]