#19750: Postgres conflict on CREATE INDEX: "relation exists"
-------------------------------------+-------------------------------------
     Reporter:  pricco@…             |                    Owner:
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:
  (models, ORM)                      |  1.5-beta-1
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by claudep):

 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 Thanks for the updated patch.
 However, I investigated some more, and I think I found the basic issue. At
 some point in time, `sql_indexes_for_field` has been customized for
 PostgreSQL because it needed some special indexes (see [f1ea26dd99415d]).
 Then, the common `sql_indexes_for_field` received several fixes and
 improvements, namely a change in the index naming using a hash of column
 names ([9d8492c169d]), without having the PostgreSQL version being
 updated.
 For example, while investigating this, I found a bug in that `sqlindexes`
 and `sqldropindexes` do not use the same index names and are therefore
 broken for PostgreSQL!
 I think that the proper fix for this ticket is to somewhat reconcile
 `sql_indexes_for_field` implementations. The new index naming usage will
 automatically fix the current issue.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19750#comment:8>
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/074.20eaee86cbebf56cad133c4d959ec2ca%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to