| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deadlock while re-indexing table |
| Date: | 2008-02-12 15:37:15 |
| Message-ID: | 26623.1202830635@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chander Ganesan | 2008-02-12 15:38:45 | Re: Some Autovacuum Questions |
| Previous Message | Alvaro Herrera | 2008-02-12 15:35:20 | Re: Some Autovacuum Questions |