Re: Selecting strict, immutable text for a composite type.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steven Lembark <lembark(at)wrkhors(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Selecting strict, immutable text for a composite type.
Date: 2018-05-10 18:41:26
Message-ID: 30030.1525977686@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

[ please keep the list cc'd ]

Steven Lembark <lembark(at)wrkhors(dot)com> writes:
> On Thu, 10 May 2018 11:52:48 -0400
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben Hood 2018-05-10 19:57:23 Re: Domain based on TIMEZONE WITH TIME ZONE
Previous Message Adrian Klaver 2018-05-10 17:29:00 Re: Domain based on TIMEZONE WITH TIME ZONE