Client is running 7.4.6 right now (we're looking at moving to 7.4.8 when
we can get a suitable ops window for the upgrade), and is experiencing
semi-regular (10-16 times a day) deadlocks, with the following
information:
A little background:
1) We do not do explicit row or table locking.
I haven't had much experience (okay, I've yet to use it) with tsearch2,
but according to
http://www.postgresql.org/docs/8.0/interactive/limitations.html, GiST
does have concurrency issues The current implementation of GiST within
PostgreSQL has some major limitations: GiST access is not
Marc G. Fournier [EMAIL PROTECTED] writes:
...
3) All deadlocks are fighting for the same relation: 4335271, which is
the tsearch2 fulltext index on the articles table:
articles_idxft1_idx.
DETAIL: Process 8122 waits for AccessExclusiveLock on relation 4335271 of
database
