| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Deadlock with tsearch2 index ... |
| Date: | 2005-05-31 17:41:14 |
| Message-ID: | 20050531143855.K933@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2005-05-31 17:45:56 | Major flood of mail to lists ... |
| Previous Message | Tom Lane | 2005-05-31 16:27:18 | Re: Cost of XLogInsert CRC calculations |