Re: [GENERAL] Indexed leading substring searches - worked, now doesn't

2005-02-03 Thread Tom Lane
Wes <[EMAIL PROTECTED]> writes: > As an interim solution until I can reload the database (takes a weekend), > can I define two indexes on the same field, one using operator classes and > one not (and have them automatically used as appropriate)? Certainly. regards, tom lan

Re: [GENERAL] Indexed leading substring searches - worked, now

2005-02-03 Thread Wes
On 2/3/05 2:29 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote: > You could use the alternative operator classes for pattern searches, but > if you want the same indexes to also serve for normal text sorting, > C locale is the better bet. As an interim solution until I can reload the database (takes a w

Re: [GENERAL] Indexed leading substring searches - worked, now doesn't

2005-02-03 Thread Tom Lane
Wes <[EMAIL PROTECTED]> writes: > The locale is showing up as en_US.iso885915. As far as I know, it was > always this (default RedHat install), so I don't understand why it worked > before. Did something change between 7.4.1 and 7.4.5? I supposed it's > possible that I specified locale=C on the

[GENERAL] Indexed leading substring searches - worked, now doesn't

2005-02-03 Thread Wes
I know my leading substring searches used to be done via indexes. We specifically tested that. Since the last time I tested it, the database has probably been reloaded to fix a corruption problem. Now all I can get is sequential leading substring searches. In the examples below, the database wa