Re: deadlock while re-indexing table

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Dave Cramer wrote:
>> reindex table user_profile;
>> ERROR:  deadlock detected
>> DETAIL:  Process 32450 waits for AccessExclusiveLock on relation
>> 194689112 of database 163880909; blocked by process 31236.
>> Process 31236 waits for AccessShareLock on relation 194689110 of
>> database 163880909; blocked by process 32450.

> I don't find this very surprising ... I would suggest using "reindex
> index" for each index instead.  I'm not sure if REINDEX TABLE is
> supposed to be deadlock-free.

It's not guaranteed to be so, but I'd think simple cases would be
okay.  What's that other process doing?

            regards, tom lane