| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Tweaking PG (again) |
| Date: | 2008-11-14 15:23:00 |
| Message-ID: | 25976.1226676180@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com> writes:
> 2. Is there a production equivalent of REINDEX? Last time I tried
> CREATE INDEX CONCURRENTLY overnight, by the morning it had croaked
> with these errors:
> ERROR: deadlock detected
> DETAIL: Process 6663 waits for ShareLock on transaction 999189656;
> blocked by process 31768.
> Process 31768 waits for ShareUpdateExclusiveLock on relation 50002 of
> database 41249; blocked by process 6663
Can't help you on that unless you can show us what else you were doing.
It's hard to see how the above could have happened unless the CREATE
INDEX CONCURRENTLY were inside a transaction that had already made other
updates that conflicted with what some other transaction wanted to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-11-14 15:56:21 | Re: Delete cascade trigger runs security definer |
| Previous Message | tv | 2008-11-14 15:14:03 | Re: Tweaking PG (again) |