Re: [GENERAL] Tweaking PG (again) - postgresql
This is a discussion on Re: [GENERAL] Tweaking PG (again) - postgresql ; "Phoenix Kiula" 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 ...
![]() |
| | LinkBack | Thread Tools | Display Modes |
|
#1
| |||
| |||
| > 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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general |
![]() |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
| |
All times are GMT -4. The time now is 07:30 PM.




Linear Mode