[rt-users] postgres slowdowns? (pg 7.3.4, rt 3.0.4)

[Jim Rowan]

I'd suggest that you just force the emailaddress to be lowercased when
it is entered or modified.  Pay the penalty once on entry, instead of
thousands of times an hour...  I can't think of any reason that you WANT
to preserve the case.

> -----Original Message-----
> From: Justin Hawkins [mailto:justin at internode.com.au] 
...
> > 
> > Or create an index on lower(EmailAddress) on that table:
> > 
> > CREATE INDEX users5 ON users (lower(emailaddress));
> > 
> > see if that speeds it up, since PG will then be able to use 
> the index.  
> > It sounds like the users5 index is unused, since the query is not 
> > against a fixed string but on a function.
> 
> Tried, but no dice. Are you interested in seeing the postgres 
> EXPLAIN output's before and after the index?
> 
> I tested the ILIKE solution and it does work. It reduces 
> query time to less than one second. I expect this may not be 
> suitable in terms of keeping this 
> cross-database-platform compatible.
> 
> 	- Justin
> _______________________________________________
> rt-users mailing list
> rt-users at lists.fsck.com 
> http://lists.fsck.com/mailman/listinfo/rt-> users
> 
> Have you 
> read the FAQ? The RT FAQ Manager lives at 
> http://fsck.com/rtfm
>