On 6/29/2013 9: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.
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.
you need an INDEX on lower(field) or upper(field). this is only
computed when values are inserted.
if you like a specific feature of SQL Server, then by all means, use SQL
Server. postgres does not and will not support automatic case
insensitive data.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
