From: | David Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | PostgreSQL Performance List <pgsql-performance(at)postgresql(dot)org> |
Subject: | Performance of DOMAINs |
Date: | 2006-06-21 18:26:16 |
Message-ID: | 54D833BE-A58F-47B8-B070-2AEDC0802468@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Howdy,
Didn't see anything in the archives, so I thought I'd ask: has anyone
done any work to gauge the performance penalty of using DOMAINs? I'm
thinking of something like Elein's email DOMAIN:
http://www.varlena.com/GeneralBits/
I figured that most simple domains that have a constraint check are
no faster or slower than tables with constraints that validate a
particular column. Is that the case?
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?
Many TIA,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-06-21 18:33:05 | Re: Big array speed issues |
Previous Message | Tom Lane | 2006-06-21 17:12:11 | Re: Speeding up query, Joining 55mil and 43mil records. |