From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | bhanu udaya <udayabhanu1984(at)hotmail(dot)com> |
Cc: | Kevin Grittner <kgrittn(at)mail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: Postgres case insensitive searches |
Date: | 2013-06-29 19:08:15 |
Message-ID: | 51CF309F.4010506@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support 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
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Tiffin | 2013-06-29 19:08:47 | Re: Postgres case insensitive searches |
Previous Message | John R Pierce | 2013-06-29 17:38:24 | Re: Postgres case insensitive searches |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Tiffin | 2013-06-29 19:08:47 | Re: Postgres case insensitive searches |
Previous Message | John R Pierce | 2013-06-29 17:38:24 | Re: Postgres case insensitive searches |