> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 16 January 2004 21:50
> To: Martin Hampl
> Cc: [EMAIL PROTECTED]; Mark Cave-Ayland
> Subject: Re: [GENERAL] indexing with lower(...) -> queries
> are not optimised very well - Please He
Am 21.11.2003 um 06:54 schrieb Tom Lane:
Martin Hampl <[EMAIL PROTECTED]> writes:
Index Scan using word_lower_idx on token (cost=0.00..98814.08
rows=25382 width=16)
Index Cond: (lower((word)::text) = 'saxophone'::text)
The rows estimate (and therefore also the cost estimate) is a complete
g
Hi,
I am using PostgreSQL 7.4, but I did have the same problem with the
last version.
I indexed the column word (defined as varchar(64)) using lower(word).
If I use the following query, everything is fine, the index is used and
the query is executed very quickly:
select * from token where
