Opened 7 years ago
Closed 7 years ago
#28448 closed New feature (duplicate)
Support concurrently indexes for PostgreSQL
| Reported by: | Mads Jensen | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | dev |
| Severity: | Normal | Keywords: | db-indexes concurrently postgres |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (2)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Component: | Database layer (models, ORM) → Migrations |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
I reopened #21039 and am closing this as a duplicate.
Note:
See TracTickets
for help on using tickets.
Related to #21039. This should be doable through class based indexes but I'm not sure what is the best solution here, add
concurrentto the base index class and error out on unsupported backends or provide it throughdjango.contrib.postgres.