[Django] #24357: Renaming Foreignkey field leaves index

[Django]

#24357: Renaming Foreignkey field leaves index
----------------------------+--------------------
Reporter: poirier | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------
Basically, if I start with a field 'field' that is a foreign key with
db_index=True (the default), rename it to 'field2', then add a new foreign
key named 'field', executing the migration fails when it comes to adding
the new field due to a db index already existing that it's trying to
create again.

I'll attach a tarball with a minimal Django project and script to recreate
it.

I've tried this with Postgres 9.3 and Django 1.7.3 and 1.7.4.

--
Ticket URL: <https://code.djangoproject.com/ticket/24357>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#24357: Renaming Foreignkey field leaves index

----------------------------+--------------------------------------
Reporter: poirier | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0

----------------------------+--------------------------------------
Changes (by poirier):

* status: new => closed
* needs_docs: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_better_patch: => 0

Comment:

Oops, looks like a dup of https://code.djangoproject.com/ticket/23577

--
Ticket URL: <https://code.djangoproject.com/ticket/24357#comment:1>