Deadlock with tsearch2 index ... - Mailing list pgsql-hackers

From Marc G. Fournier
Subject Deadlock with tsearch2 index ...
Date
Msg-id 20050531143855.K933@ganymede.hub.org
Whole thread Raw
Responses Re: Deadlock with tsearch2 index ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Deadlock with tsearch2 index ...  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
Just want to make sure that this is, in fact, what is expected:

client1: begin;
client1: update articles set some_col = <foo> where id = <bar>;
client2: update articles set some_col2 = <foo2> where id = <bar>;
client1: update articles set some_col3 = <foo> where id = <bar>;
client1: ** deadlock **

client2 can't finish its 'transaction', and is therefore preventing 
client1 from continuing ... ?

Assuming that this is, in fact, 'normal', is there a way of breaking the 
deadlock?

If this is *not*, in fact, 'normal', is there any more information that I 
can provide to debug this?

This is a 7.4.6 database right now ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664


pgsql-hackers by date:

Previous
From: "Mya Mason"
Date:
Subject: new antidote found
Next
From: Manfred Koizar
Date:
Subject: Re: Cost of XLogInsert CRC calculations