#34898: Adding non-deterministic collations to unique CharFields crashes on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Tom
| Carrick
Type: Bug | Status: assigned
Component: Migrations | Version: 4.2
Severity: Normal | Resolution:
Keywords: PostgreSQL | Triage Stage: Accepted
collation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:5 Tom Carrick]:
> I agree that it's consistent. What I don't think is a good idea though,
is dropping and recreating the entire index. This could take a fairly long
time on some databases, and it can be quite surprising that a change to
the collation would cause another operation that takes some time.
>
> I can have a look though. Maybe we can at least do it concurrently.
Can we recreate them? For now, we completely skip
`varchar_pattern_ops`/`text_pattern_ops` indexes when non-deterministic
`db_collation` is set. Is it not enough to remove them before adding a
collation?
--
Ticket URL: <https://code.djangoproject.com/ticket/34898#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/0107018bd232bf0a-6f95ec26-8f90-4d67-9054-50bf14f3ad05-000000%40eu-central-1.amazonses.com.
