Re: Weird locking situation - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Weird locking situation
Date
Msg-id 3F7E951F.9060402@familyhealth.com.au
Whole thread Raw
In response to Re: Weird locking situation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> 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 ...

Wow, that's bad.  I always thought the TODO item was talking about poor 
concurrent performance - not actual concurrency errors!

Chris




pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Quick question
Next
From: "Andrew Dunstan"
Date:
Subject: Re: Using backslash in query