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

Re: Weird locking situation

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Weird locking situation
Date: 2003-10-03 14:48:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, 3 Oct 2003, Tom Lane wrote:

> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > OK, I tried it again and it still seems buggy to me...
> > I wonder if it's something to do with the tsearch trigger on food_foods?
> I tried a table with a simple BEFORE trigger and it didn't fail.
> But when I added a GIST index, it did:
> [ install contrib/btree_gist ]
> regression=# create index gindex on foo using gist (f2);
> ...
> regression=# UPDATE foo SET f2=now() WHERE f1=1;
> ERROR:  deadlock detected
> DETAIL:  Process 18122 waits for AccessExclusiveLock on relation 154635 of database 17139; blocked by process 18133.
> Process 18133 waits for ShareLock on transaction 6330; blocked by process 18122.
> The trouble here is that GIST indexes are not concurrency-safe.
> This is on the TODO list but I fear it's not a small task ...

You're right. We hoped to work on concurrency this year and already
did some research. But life is so complicated :(

> 			regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su,
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-10-03 15:03:19
Subject: Re: HeapTuple->t_tableOid==0 after SPI_exec
Previous:From: Tom LaneDate: 2003-10-03 14:43:36
Subject: Re: HeapTuple->t_tableOid==0 after SPI_exec

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