Re: Case Insensitive

From: Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com>
To: Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>
Cc: Steve Atkins <steve(at)blighty(dot)com>, PG mailing List <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Case Insensitive
Date: 2019-03-28 09:05:54
Message-ID: CAGuFTBVFBTowoOr9gjbB2kqnSQ0QVSDcEb8xhgvrAGNeuMbmxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

With ILIKE or extension CITEXT, does it have any impact on Indexes, like
not picking index ?

ILIKE works only for operator LIKE not for operator =

CITEXT seems some possibilities,

Thanks
Sridhar

On Thu, Mar 28, 2019 at 2:07 PM Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com>
wrote:

>
>
> On Thu, 28 Mar, 2019, 4:33 PM Steve Atkins, <steve(at)blighty(dot)com> wrote:
>
>>
>>
>> > On Mar 28, 2019, at 8:29 AM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>> >
>> > On 3/28/19 3:23 AM, Sameer Kumar wrote:
>> > [snip]
>> >> You can write a query with upper function:
>> >>
>> >> select * from emp where upper(ename)=upper('aaa');
>> >
>> > That's a guaranteed table scan.
>>
>> Unless you have an index on upper(ename).
>>
>
> Yup, with this or overloading "=", one can create an expression based
> index and benefit from it.
>
>
>> Cheers,
>> Steve
>>
>>
>>
>>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2019-03-28 09:08:48 Re: Case Insensitive
Previous Message Sameer Kumar 2019-03-28 08:37:10 Re: Case Insensitive

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2019-03-28 09:08:48 Re: Case Insensitive
Previous Message Sameer Kumar 2019-03-28 08:37:10 Re: Case Insensitive