--
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von
John Sidney-Woollett
Gesendet: Donnerstag, 17. Juni 2004 11:36
An: Henrik Steffen
Cc: 'Scott Marlowe'; pgsql
Betreff: Re: [GENERAL] index with LIKE
Henrik Steffen wrote:
hello scott,
disable enable_seqscan s
11:36
> An: Henrik Steffen
> Cc: 'Scott Marlowe'; pgsql
> Betreff: Re: [GENERAL] index with LIKE
>
>
> Henrik Steffen wrote:
>
> >hello scott,
> >
> >disable enable_seqscan still does no force the backend
> >to use indexes.
> >
Henrik Steffen wrote:
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:
typemainserver slave
lc_collate Cde_DE.UTF-8
lc_ctype[EMAIL PROTECTED] de_DE.UTF-8
lc
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:
typemainserver slave
lc_collate Cde_DE.UTF-8
lc_ctype[EMAIL PROTECTED] de_DE.UTF-8
lc_messages [EMAIL
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 y
hi tom,
here the results of
EXPLAIN ANALYZE SELECT * FROM basiseintrag WHERE kundennummer LIKE
'0101%' AND firma LIKE 'top con%';
run on all three servers:
main server:
QUERY PLAN
--
Martijn van Oosterhout wrote:
The classic issue is what encoding are the databases. Anything other
than C and like won't use indexes.
Unless you use text_pattern_ops. See
http://www.postgresql.org/docs/7.4/static/indexes-opclass.html
I think this needs to be in the faq.
-
