Re: String comparision in PostgreSQL - Mailing list pgsql-general

From Nicola Cisternino
Subject Re: String comparision in PostgreSQL
Date
Msg-id 503E3B91.2040107@tiscali.it
Whole thread Raw
In response to Re: String comparision in PostgreSQL  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: String comparision in PostgreSQL  (Chris Angelico <rosuav@gmail.com>)
Re: String comparision in PostgreSQL  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-general
Il 29/08/2012 17.08, Merlin Moncure ha scritto:
On Tue, Aug 28, 2012 at 9:46 AM, Nicola Cisternino <ncister@tiscali.it> wrote:
Hi all,
I'm valutating a complex porting of our application based on Sybase
SqlAnywhere on PostgreSQL (I've love it ...) and I'd like to have your
opinion about searching/ordering funcionality.
The problem is about string comparision.
MS Sql server, MySql, SqlAnywhere and other DB engine allow a simple
definition of case sensitive/insensitive behavior using char, varchar and
text field type.
In PostgreSQL I've already tried to use "citext", lower() function (applied
to indexes, too ...), ILIKE an so on ..... but nothing really work as I need
(poor performances ...) !!
hm, poor performance? can you elaborate?

merlin
The same query using " .... LIKE <value> ...." is completed in 15 ms while using " .... ILIKE <value> ...." the execution time is 453 ms ....

pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: [postgis-users] pg_dump -s should use add_geometrycolumn(...)
Next
From: Tom Lane
Date:
Subject: Re: [postgis-users] pg_dump -s should use add_geometrycolumn(...)