[Django] #28448: Support concurrently indexes for PostgreSQL

5 views
Skip to first unread message

Django

unread,
Jul 29, 2017, 2:37:08 AM7/29/17
to django-...@googlegroups.com
#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.

Django

unread,
Jul 29, 2017, 7:53:27 AM7/29/17
to django-...@googlegroups.com
#28448: Support concurrently indexes for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Mads Jensen | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: db-indexes | Triage Stage:
concurrently postgres | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

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>

Django

unread,
Jul 29, 2017, 9:57:29 AM7/29/17
to django-...@googlegroups.com
#28448: Support concurrently indexes for PostgreSQL
-------------------------------------+-------------------------------------
Reporter: Mads Jensen | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: duplicate

Keywords: db-indexes | Triage Stage:
concurrently postgres | Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):

* 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>

Reply all
Reply to author
Forward
0 new messages