Re: [HACKERS] REINDEX CONCURRENTLY 2.0
| От | Robert Haas |
|---|---|
| Тема | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |
| Дата | |
| Msg-id | CA+TgmoZW=rowSzYUzjVJ1kF8zH5NQYcHrhuRNJ_Z9DxBb-Q3Rw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 (Vik Fearing <vik.fearing@2ndquadrant.com>) |
| Ответы |
Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |
| Список | pgsql-hackers |
On Fri, Jan 18, 2019 at 9:01 PM Vik Fearing <vik.fearing@2ndquadrant.com> wrote: > I don't want a situation like this: > CREATE INDEX CONCURRENTLY ... > DROP INDEX CONCURRENTLY ... > REINDEX INDEX (CONCURRENTLY) ... > > All three should be the same, and my suggestion is to add the > parenthesized version to CREATE and DROP and not add the unparenthesized > version to REINDEX. +1 for all three being the same. I could see allowing only the unparenthesized format for all three, or allowing both forms for all three, but I think having only one form for each and having them not agree will be too confusing. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: