Re: Performance of DOMAINs

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: David Wheeler <david(at)kineticode(dot)com>
Subject: Re: Performance of DOMAINs
Date: 2006-06-22 01:19:07
Message-ID: 200606211819.08239.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

David,

> But I'm also interested in how Elein made the email domain case-
> insensitive, since I'd like to have/create a truly case-insensitive
> text type (ITEXT anyone?). The functions for the operator class there
> were mainly written in SQL, and if it adds a significant overhead,
> I'm not sure it'd be a good idea to use that approach for a case-
> insensitive text type, since I use it quite a lot in my apps, and
> often do LIKE queries against text data. Thoughts?

Well, current case-insensitivity hacks definitely aren't compatible with
LIKE as far as "begins with" indexes are concerned. Of course, floating
LIKEs (%value%) are going to suck no matter what data type you're using.

I created an operator for CI equality ... =~ ... which performs well on
indexed columns. But it doesn't do "begins with".

ITEXT is a TODO, but there are reasons why it's harder than it looks.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Glaesemann 2006-06-22 02:24:22 Re: Performance of DOMAINs
Previous Message jody brownell 2006-06-21 23:08:55 Re: Help tuning autovacuum - seeing lots of relationbloat