From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: David Wheeler <david@kineticode.com>
Subject: Re: Performance of DOMAINs
Date: Wed, 21 Jun 2006 18:19:07 -0700
Message-ID: <200606211819.08239.josh@agliodbs.com> (raw)
In-Reply-To: <54D833BE-A58F-47B8-B070-2AEDC0802468@kineticode.com>
References: <54D833BE-A58F-47B8-B070-2AEDC0802468@kineticode.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, david@kineticode.com
Subject: Re: Performance of DOMAINs
In-Reply-To: <200606211819.08239.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox