By default, all indexes are created inside a transaction which does not
work together with `concurrently`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by Simon Charette):
Related to #21039. This should be doable through class based indexes but
I'm not sure what is the best solution here, add `concurrent` to the base
index class and error out on unsupported backends or provide it through
`django.contrib.postgres`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28448#comment:1>
* status: new => closed
* component: Database layer (models, ORM) => Migrations
* resolution: => duplicate
Comment:
I reopened #21039 and am closing this as a duplicate.
--
Ticket URL: <https://code.djangoproject.com/ticket/28448#comment:2>