#35383: Add support for `IF NOT EXISTS` when creating postgres indexes 
concurrently
-------------------------------------+-------------------------------------
     Reporter:  Marcelo              |                    Owner:  (none)
         Type:  New feature          |                   Status:  closed
    Component:  contrib.postgres     |                  Version:  5.0
     Severity:  Normal               |               Resolution:  duplicate
     Keywords:  database, postgres,  |             Triage Stage:
  index, concurrently                |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

 * resolution:   => duplicate
 * status:  new => closed

Comment:

 Duplicate of #34729 which was also discussed and resolved as wontfix.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35383#comment:3>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018eefd49df4-0ad7ca40-c0f3-446b-8c4d-3fdf7949ede5-000000%40eu-central-1.amazonses.com.

Reply via email to