deadlocks in multiple-triggers environment

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: deadlocks in multiple-triggers environment
Date: 2005-06-08 15:45:45
Message-ID: 9e4684ce05060808453f6b9cdd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2005-06-08 15:49:02 Re: Bug with view definition?
Previous Message Dan Black 2005-06-08 15:40:57 Foreign keys and slow insert