>> You may also be able to get away with another index on the column
>> using text_pattern_ops as the operator class if you need/want other
>> en_US features.
>
>Suppose I got to en_US by accident and need none of its features. Is
>there a reason any reason I should initdb --locale=C and restore?
>
>What benefits and detriments does en_US have over C? I'm having a hard
>time caring which I use (as long they give what I want).
The text_pattern_ops index will not work on UPPER(field) LIKE 'AAA%'
queries. My experience as of 7.4.6.