I have a similar problem.
In an attempt to avoid the overhead of select count(*) from mailbox
where uid = somuid I've implemented triggers on insert and delete.
So there is a
user table which refers to to an inbox table,
so when people insert into the inbox there is an RI trigger grabbing
the shared lock, then the count triggers try to grab an exclusive
lock resulting in a deadlock.
Can we safely remove the shared locks ?
Is there a right way to implement the count triggers. I've tried
before triggers, and after triggers, both result in different kinds
On 18-Apr-07, at 11:36 AM, Csaba Nagy wrote:
>> Can someone confirm that I've identified the right fix?
> I'm pretty sure that won't help you... see:
> The deadlock will be there if you update/insert the child table and
> update/insert the parent table in the same transaction (even if you
> update some other field on the parent table than the key referenced by
> the child table). If your transactions always update/insert only
> one of
> those tables, it won't deadlock (assuming you order the inserts/
> properly per PK).
> ---------------------------(end of
> TIP 5: don't forget to increase your free space map settings
In response to
pgsql-performance by date
|Next:||From: Alvaro Herrera||Date: 2007-04-19 14:14:42|
|Subject: Re: Foreign Key Deadlocking|
|Previous:||From: Merlin Moncure||Date: 2007-04-19 00:16:18|
|Subject: Re: Basic Q on superfluous primary keys|