#28448: Support concurrently indexes for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Mads | Owner: nobody
Jensen |
Type: New | Status: new
feature |
Component: Database | Version: master
layer (models, ORM) | Keywords: db-indexes
Severity: Normal | concurrently postgres
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Support for `CREATE INDEX CONCURRENTLY` on PostgreSQL would be a plus. I
think it was previously discussed to add it as the default behavior, but
that probably has undesired side-effects for some cases. I imagine
`concurrently=False` as an option to the index-class.
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.
--
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.e77aaafb4a8f551d59acdbc45d5cc673%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
