Skip site navigation (1) Skip section navigation (2)

Re: Attempting to disable count triggers on cleanup

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: depesz(at)depesz(dot)com
Cc: postgresql performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Attempting to disable count triggers on cleanup
Date: 2007-09-25 11:39:42
Message-ID: 46F8F37E.9060204@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-performance
hubert depesz lubaczewski wrote:
> On Tue, Sep 25, 2007 at 07:08:42AM -0400, Dave Cramer wrote:
>   
>> ERROR:  deadlock detected
>> DETAIL:  Process 23063 waits for ExclusiveLock on tuple (20502,48) of 
>> relation 48999028 of database 14510214; blocked by process 23110.
>> Process 23110 waits for ShareLock on transaction 1427023217; blocked by 
>> process 23098.
>> ...
>> CONTEXT:  SQL statement "update user_profile_count set 
>> buddycount=buddycount-1 where user_profile_count.uid= $1 "
>> PL/pgSQL function "user_buddy_count" line 11 at SQL statement
>> SQL statement "DELETE FROM ONLY "public"."user_buddies" WHERE 
>> "buddyuserid" = $1"
>>     
>
> take a look at:
> http://www.depesz.com/index.php/2007/09/12/objects-in-categories-counters-with-triggers/
>
> and if you want to temporarily disable trigger, simply do appropriate
> "alter table disable trigger".
>
>   
Well, that doesn't work inside a transaction I've tried it. This has 
been fixed in 8.3

Dave
> depesz
>
>   


In response to

pgsql-performance by date

Next:From: Kamen StanevDate: 2007-09-25 19:41:03
Subject: Re: query io stats and finding a slow query
Previous:From: hubert depesz lubaczewskiDate: 2007-09-25 11:21:49
Subject: Re: Attempting to disable count triggers on cleanup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group