Re: Catalog Access (was: [GENERAL] Concurrency problem
От | Tom Lane |
---|---|
Тема | Re: Catalog Access (was: [GENERAL] Concurrency problem |
Дата | |
Msg-id | 21858.1146091373@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Catalog Access (was: [GENERAL] Concurrency problem ("Jim C. Nasby" <jnasby@pervasive.com>) |
Ответы |
Re: Catalog Access (was: [GENERAL] Concurrency problem
Re: Catalog Access (was: [GENERAL] Concurrency problem |
Список | pgsql-hackers |
"Jim C. Nasby" <jnasby@pervasive.com> writes: > Try running a first index build by itself and then running them in > parallel. Yeah, this is probably the best workaround for now. I think we should look at making it fully concurrent-safe per upthread comments, but that won't be happening in existing release branches. Also, the only case where it's a problem is if the first two index builds finish at almost exactly the same time. It might be possible to overlap the first two index builds with reasonable safety so long as you choose indexes with very different sorting costs (eg, integer vs text columns, different numbers of columns, etc). regards, tom lane
В списке pgsql-hackers по дате отправления: