Re: String comparision in PostgreSQL

From: Nicola Cisternino <ncister(at)tiscali(dot)it>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: String comparision in PostgreSQL
Date: 2012-08-29 15:56:01
Message-ID: 503E3B91.2040107@tiscali.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Il 29/08/2012 17.08, Merlin Moncure ha scritto:
> On Tue, Aug 28, 2012 at 9:46 AM, Nicola Cisternino<ncister(at)tiscali(dot)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 ....

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-08-29 16:02:24 Re: [postgis-users] pg_dump -s should use add_geometrycolumn(...)
Previous Message Andres Freund 2012-08-29 15:46:03 Re: [postgis-users] pg_dump -s should use add_geometrycolumn(...)