Re: CREATE INDEX CONCURRENTLY?

Поиск
Список
Период
Сортировка
Искать
От
Greg Stark
Тема
Re: CREATE INDEX CONCURRENTLY?
Дата
Msg-id
CAM-w4HOpoXYHnYOh27j87W9UT_4y0M0S-n_fWghRpFmZ-uLqjg@mail.gmail.com
Ответ на
Список
Дерево обсуждения
CREATE INDEX CONCURRENTLY? Mark Woodward <mark.woodward@actifio.com>
Re: CREATE INDEX CONCURRENTLY? Andrew Dunstan <andrew@dunslane.net>
Re: CREATE INDEX CONCURRENTLY? Greg Stark <stark@mit.edu>
Re: CREATE INDEX CONCURRENTLY? Michael Banck <michael.banck@credativ.de>
Re: CREATE INDEX CONCURRENTLY? Simon Riggs <simon@2ndQuadrant.com>
Re: CREATE INDEX CONCURRENTLY? Tim Kane <tim.kane@gmail.com>
On Fri, Oct 31, 2014 at 2:28 PM, Mark Woodward
 wrote:
> I have not kept up with PostgreSQL changes and have just been using it. A
> co-worker recently told me that you need to word "CONCURRENTLY" in "CREATE
> INDEX" to avoid table locking. I called BS on this because to my knowledge
> PostgreSQL does not lock tables. I referenced this page in the
> documentation:


You can read from tables while a normal index build is in progress but
you can't insert, update, or delete from them. CREATE INDEX
CONCURRENTLY allows you to insert, update, and delete data while the
index build is running at the expense of having the index build take
longer.

-- 
greg


В списке pgsql-hackers по дате отправления
От: Andrew Dunstan
Дата:
Сообщение: Re: CREATE INDEX CONCURRENTLY?
От: Simon Riggs
Дата:
Сообщение: Re: Reducing Catalog Locking
FAQ