Re: Custom Operator for citext LIKE predicates question

From: "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Custom Operator for citext LIKE predicates question
Date: 2022-01-13 17:20:36
Message-ID: 2111588120.340821.1642094436477@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Good points. At least on the limited testing we did, we were able to get the same answer back with both executions; at least for the use cases we tested. 
We are still doing more thourough testing.
This is an application that is been ported from MS SQL server to postgres and apparently the migration dba team determined citext was the way to go to maintain MSSQL existing usage of the data in the columns.

Thanks,Efrain J. Berdecia

On Thursday, January 13, 2022, 10:10:38 AM EST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

"Efrain J. Berdecia" <ejberdecia(at)yahoo(dot)com> writes:
> In our setup it has actually worked per the explains provided making the query run in milliseconds instead of seconds.

To me, "work" includes "get the right answer".  I do not think you
are getting the same answers that citext would normally provide.
If you don't care about case-insensitivity, why don't you just
use plain text?

            regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-01-13 17:41:27 Re: Schema variables - new implementation for Postgres 15
Previous Message Robert Haas 2022-01-13 17:18:39 Re: Avoiding smgrimmedsync() during nbtree index builds