Re: Weird locking situation

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Weird locking situation
Date: 2003-10-03 02:13:09
Message-ID: 3F7CDB35.9030406@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> I wonder if it's something to do with the tsearch trigger on food_foods?

Actually, it definitely seems to be the tsearch trigger. The deadlock
occurs on every table that uses tsearch trigger, and no table that doesn't.

It's probably not the tsearch trigger itself even, it's probably the
fact that the tsearch trigger modifies the row during the update in the
second session?

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-10-03 02:18:48 Quick question
Previous Message Christopher Browne 2003-10-03 02:08:18 Re: count(*) slow on large tables