| From: | Neil Tiffin <neilt(at)neiltiffin(dot)com> |
|---|---|
| To: | bhanu udaya <udayabhanu1984(at)hotmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres case insensitive searches |
| Date: | 2013-06-29 19:08:47 |
| Message-ID: | ADB34248-D74F-4992-B213-297A760450B6@neiltiffin.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-general |
On Jun 29, 2013, at 11:24 AM, bhanu udaya <udayabhanu1984(at)hotmail(dot)com> wrote:
> Upper and Lower functions are not right choice when the table is > 2.5 million and where we also have heavy insert transactions.
PostgreSQL and SQL Server are completely different. Rules that apply to SQL Server do not necessarily apply to PostgreSQL.
You problem is not the use of upper() or lower() it is the assumption what works in SQL Server is the best way to use PostgreSQL. You'll get farther if you benchmark several of the suggestions, then if the performance is not good enough, ask how to improve the performance. This will take a little work on your part, but that is how you learn.
Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Shapiro | 2013-06-29 22:59:46 | Re: [pgadmin-support] Postgres case insensitive searches |
| Previous Message | Joshua D. Drake | 2013-06-29 19:08:15 | Re: Postgres case insensitive searches |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Shapiro | 2013-06-29 22:59:46 | Re: [pgadmin-support] Postgres case insensitive searches |
| Previous Message | Joshua D. Drake | 2013-06-29 19:08:15 | Re: Postgres case insensitive searches |