Re: Should I implement DROP INDEX CONCURRENTLY?
| От | Simon Riggs |
|---|---|
| Тема | Re: Should I implement DROP INDEX CONCURRENTLY? |
| Дата | |
| Msg-id | CA+U5nMJycjsHcu__qC4nxu7nyn2F7eF08hX=z=oHu873nzhiDg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Should I implement DROP INDEX CONCURRENTLY? (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: Should I implement DROP INDEX CONCURRENTLY?
|
| Список | pgsql-hackers |
On Wed, Feb 1, 2012 at 7:31 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On sön, 2012-01-29 at 22:01 +0000, Simon Riggs wrote: >> Patch now locks index in AccessExclusiveLock in final stage of drop. > > Doesn't that defeat the point of doing the CONCURRENTLY business in the > first place? That was my initial reaction. We lock the index in AccessExclusiveLock only once we are certain nobody else is looking at it any more. So its a Kansas City Shuffle, with safe locking in case of people doing strange low level things. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: