#34932 closed Bug (fixed)
Setting deterministic Postgres collations incorrectly disallows use of varchar_pattern_ops and text_pattern_ops
Reported by: | Tom Carrick | Owned by: | Tom Carrick |
---|---|---|---|
Component: | Migrations | Version: | 4.2 |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Change History (7)
comment:1 by , 12 months ago
Owner: | changed from | to
---|
comment:2 by , 12 months ago
Severity: | Normal → Release blocker |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:4 by , 12 months ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
Thanks for the report. We should be able to skipped
varchar_pattern_ops/text_pattern_ops
index creation only for non-deterministic collations by introspectingpg_collation.collisdeterministic
.Regression in f3f9d03edf17ccfa17263c7efa0b1350d1ac9278 (4.2) and 8ed25d65ea7546fafd808086fa07e7e5bb5428fc (5.0).