Re: Arg! PG not using index on an analyzed table

From: Reece Hart <reece(at)harts(dot)net>
To: SF PostgreSQL <sfpug(at)postgresql(dot)org>
Subject: Re: Arg! PG not using index on an analyzed table
Date: 2005-02-02 20:10:48
Message-ID: 1107375049.10110.23.camel@tallac.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: sfpug

On Wed, 2005-02-02 at 11:10 -0800, Stephan Szabo wrote:

> 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).

Thanks,
Reece

--
Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0

In response to

Browse sfpug by date

  From Date Subject
Next Message Stephan Szabo 2005-02-02 20:41:25 Re: Arg! PG not using index on an analyzed table
Previous Message Reece Hart 2005-02-02 20:08:09 Re: Arg! PG not using index on an analyzed table