Re: REINDEX CONCURRENTLY 2.0
От | Robert Haas |
---|---|
Тема | Re: REINDEX CONCURRENTLY 2.0 |
Дата | |
Msg-id | CA+TgmoZ=0NMfMVjemYjO0zWFi8PS3OMZCEsqimcgc34U8UKQeg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: REINDEX CONCURRENTLY 2.0 (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: REINDEX CONCURRENTLY 2.0
Re: REINDEX CONCURRENTLY 2.0 |
Список | pgsql-hackers |
On Wed, Nov 12, 2014 at 4:10 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Thu, Nov 6, 2014 at 9:50 AM, Peter Eisentraut <peter_e@gmx.net> wrote: >> If REINDEX cannot work without an exclusive lock, we should invent some >> other qualifier, like WITH FEWER LOCKS. > > What he said. But more to the point .... why, precisely, can't this work without an AccessExclusiveLock? And can't we fix that instead of setting for something clearly inferior? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: