#30867: Old indexes should be dropped after new ones are created.
--------------------------------------+------------------------------------
Reporter: Simon Charette | Owner: nobody
Type: Cleanup/optimization | 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 Simon Charette):
> I would also add that at some point, you should assume the fact you are
using a database not supporting transactional DDL.
FWIW I'm trying to figure out if it does make a difference on backends
that support transactional DDL as well.
For example, it's not completely crazy to assume that PostgreSQL could use
an existing index on a column it's trying to create a unique constraint on
to speed up the operation given B-trees are used for both implementations.
If that's the case deferring the index removal could be beneficial to
other backends as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/30867#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.69f12e87867314d001c0615f574c2f7c%40djangoproject.com.
