You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
Our Postgres servers are very likely not configured with the "C" locale (but rather "UTF-8'), in which case the default operator class for the btree index on a TEXT column is not optimized for pattern matching expressions (e.g. LIKEs, prefix scans).
E.g. CREATE INDEX IF NOT EXISTS blocks_key_text_pattern_ops_idx ON public.blocks (key text_pattern_ops)
We may want to leave the existing btree index on key (from its UNIQUE NOT NULL constraint), as the default operator class index is optimized for ordinary <, <=, >, or >= comparisons.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our Postgres servers are very likely not configured with the "C" locale (but rather "UTF-8'), in which case the default operator class for the btree index on a
TEXT
column is not optimized for pattern matching expressions (e.g.LIKE
s, prefix scans).E.g.
CREATE INDEX IF NOT EXISTS blocks_key_text_pattern_ops_idx ON public.blocks (key text_pattern_ops)
We may want to leave the existing btree index on
key
(from itsUNIQUE NOT NULL
constraint), as the default operator class index is optimized for ordinary <, <=, >, or >= comparisons.The text was updated successfully, but these errors were encountered: