Re: index with LIKE

hello scott,

disable enable_seqscan still does no force the backend
to use indexes.

so it looks like a locale problem, right?

I checked lc_* vars on both servers:

type        mainserver   slave
lc_collate  C            de_DE.UTF-8
lc_ctype    de_DE@euro   de_DE.UTF-8
lc_messages de_DE@euro   de_DE.UTF-8
....

I guest "lc_collate" is the problem, isn't it?




pgsql-general-owner@postgresql.org wrote:
> 1: Is index capable of being used on the slaves, or are they
> just making
> bad decisions?  Try disabling seq scans on the slave servers
> for testing
> and see if they can use the index.  Use "set enable_seqscan = FALSE;"
>
> If they can't use the index then, then they are likely in the wrong
> locale, and you'll need to re initdb them to get them to use an index.
>
> If they can use the index then we have tuning issue.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)

--

Mit freundlichem Gruß

Henrik Steffen
Geschäftsführer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.de       Tel. +49 1805 9977 501*
mail: steffen@topconcepts.de    Fax. +49 1805 9977 502*
--------------------------------------------------------
SMS Versand ab 9.9 Cent: http://sms-gw.topconcepts.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------
*) EUR 0,12/Min. (CNS24)