Re: simple case using index on windows but not on linux

From: Richard Huxton <dev(at)archonet(dot)com>
To: simon godden <sgodden(at)gmail(dot)com>
Cc: 'Postgresql Performance' <pgsql-performance(at)postgresql(dot)org>
Subject: Re: simple case using index on windows but not on linux
Date: 2006-10-04 13:47:33
Message-ID: 4523BB75.9020200@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

simon godden wrote:
> I did that, e.g. initdb --locale=C, re-created all my data and have
> exactly the same problem.
>
> I have two indexes, one with no options, and one with the varchar
> operator options.
>
> So the situation now is:
> If I do a like query it uses the index with the varchar options;
> If I do a = query, it uses the index with no options;
> If I do a < or > or any other operator, it reverts back to a seq-scan!
>
> I am on FC5 - any further ideas? Did I need to do anything specific
> about collating sequence? I thought that the --locale=C would set
> that for all options.

From psql, a "show all" command will list all your config settings and
let you check the lc_xxx values are correct.

Make sure you've analysed the database after restoring, otherwise it
will have bad stats available.

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message simon godden 2006-10-04 13:47:43 Re: simple case using index on windows but not on linux
Previous Message Brad Nicholson 2006-10-04 13:47:05 Re: PostgreSQL Caching