#21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations
-----------------------------+------------------------------------
Reporter: FunkyBob | Owner:
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 charettes):
@BlindHunter, concurrent index creation has many
[http://www.postgresql.org/docs/current/static/sql-createindex.html#SQL-
CREATEINDEX-CONCURRENTLY documented caveats] hence why it's not enabled by
default.
I don't think we should expect newcomers to Django/PostgreSQL to make sure
all their index have been correctly created even if their migration ran
fine. That's the reason we're planing to make it an ''opt-in'' feature and
not the default behavior, just like it's not the default in PostgreSQL
itself.
In the meanwhile I suggest you create your own subclass of
`Alter(Index|Unique)` operations and override `database_forward` to issue
the desired SQL.
--
Ticket URL: <https://code.djangoproject.com/ticket/21039#comment:5>
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.23920d5b28af46e5fede0a582bd65e25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
