Re: Selecting strict, immutable text for a composite type. - Mailing list pgsql-general

From Tom Lane
Subject Re: Selecting strict, immutable text for a composite type.
Date
Msg-id 30030.1525977686@sss.pgh.pa.us
Whole thread Raw
In response to Selecting strict, immutable text for a composite type.  (Steven Lembark <lembark@wrkhors.com>)
Responses Re: Selecting strict, immutable text for a composite type.  (Steven Lembark <lembark@wrkhors.com>)
List pgsql-general
[ please keep the list cc'd ]

Steven Lembark <lembark@wrkhors.com> writes:
> On Thu, 10 May 2018 11:52:48 -0400
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Maybe you should show a more concrete example of what's not working.

> The problem is with gists telling me that they cannot index
> the type. This works for enums, just not the composite type.

Oh, well, they can't.  There's no GiST opclass covering arbitrary
composite types.  This doesn't seem very surprising to me given
the lack of operators that such an opclass might accelerate.

What are you expecting an index on such a column to do for you?
If you just want a uniqueness constraint, plain btree can handle it.

            regards, tom lane


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Domain based on TIMEZONE WITH TIME ZONE
Next
From: Ben Hood
Date:
Subject: Re: Domain based on TIMEZONE WITH TIME ZONE