#21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations
-----------------------------+------------------------------------
Reporter: FunkyBob | Owner: (none)
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by Simon Charette):
> The first option seems simpler to me, at least for now, unless there is
compelling evidence that another database backend will support concurrent
index creation in the near future.
I agree with your conclusions; there's little benefit to add a
`concurrent` option to `CreateIndex` for now. If any supported database
adds support for this option in the future it should be easy enough to
deprecate `contrib.postgres.CreateIndexConcurrently`.
--
Ticket URL: <https://code.djangoproject.com/ticket/21039#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a69f680707b69333680ca30d45957fbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
