Horton

Re: Postgres case insensitive searches

Joshua D. Drake <jd@commandprompt.com>

View thread View on postgr.es
From: "Joshua D. Drake" <jd@commandprompt.com>
To: bhanu udaya <udayabhanu1984@hotmail.com>
Cc: Kevin Grittner <kgrittn@mail.com>, Adrian Klaver <adrian.klaver@gmail.com>, "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>, "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.org>, Albe Laurenz <laurenz.albe@wien.gv.at>, Chris Travers <chris.travers@gmail.com>, Magnus Hagander <magnus@hagander.net>
Date: 2013-06-29T19:08:15Z
Lists: pgsql-general 
On 06/29/2013 09:24 AM, bhanu udaya wrote:

> Upper and Lower functions are not right choice when the table is > 2.5
> million and where we also have heavy insert transactions.

Prove it. Seriously, just run a test case against it. See how it works 
for you. Inserts are generally a very inexpensive operation with Postgres.

>
> I doubt, if we can cache the table if there are frequent
> inserts/updates.  The good idea would be to get the DB to case
> insenstive configuration like SQL Server. I would go for this solution,
> if postgres supports.

Postgres does not.

And as Jon said, maybe Postgres isn't the right solution for you. That 
would be a bummer but we can't be all things to all people.


JD

-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
    a rose in the deeps of my heart. - W.B. Yeats