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

Re: Deadlock with tsearch2 index ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock with tsearch2 index ...
Date: 2005-05-31 19:20:32
Message-ID: 22756.1117567232@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> 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 ... ?

Hmm, I can see why client2 might be blocked by client1, but if client1
holds the lock it should be able to continue to update the table.

I take it from your title that this only happens if there's a tsearch2
index on the table?  Can you put together a test case?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2005-05-31 20:01:00
Subject: Re: CREATE DATABASE fails when template1 being accessed ...
Previous:From: Alvaro HerreraDate: 2005-05-31 19:08:34
Subject: Re: CREATE DATABASE fails when template1 being accessed ...

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