#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 BlindHunter):
Why don't we want to always add CONCURRENTLY statement ? It's a bit slower
but allows us to execute zero downtime updates without dirty hacks like
create "fake" migration which adds indexes and add them in management
commands with "create index concurrently".
--
Ticket URL: <https://code.djangoproject.com/ticket/21039#comment:4>
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.29bb9f908acb0ebc142b7df6d8ed4751%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
