From: | Joe Van Dyk <joe(at)tanga(dot)com> |
---|---|
To: | |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: uuids with btree_gist |
Date: | 2013-09-04 05:24:19 |
Message-ID: | CACfv+pKE1V_7BJVY7tSa6Cu3fS6vyd1dM0h2MHbQyLAT+qhO6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 3, 2013 at 1:41 PM, Martin Renters <martin(at)datafax(dot)com> wrote:
> I'm trying to use timestamp ranges to keep track of the values particular
> items had over time, but I'm unable to create a table as follows:
>
> test=# create extension btree_gist;
> CREATE EXTENSION
> test=# create table v(item uuid, lifetime tstzrange, value text,
> test(# exclude using gist (item with =, lifetime with &&));
> ERROR: data type uuid has no default operator class for access method
> "gist"
> HINT: You must specify an operator class for the index or define a
> default operator class for the data type.
> test=#
>
> It works fine if I make item a text field.
>
> test=# create table v(item text, lifetime tstzrange, value text,
> test(# exclude using gist (item with =, lifetime with &&));
> CREATE TABLE
> test=#
>
> Is there any reason that the required uuid access method isn't
> implemented? How hard is it to implement this?
>
I would also like to see btree_gist support uuid's.
I found a related thread from two years ago:
http://postgresql.1045698.n5.nabble.com/UUID-datatype-GiST-index-support-td4722960.html
From | Date | Subject | |
---|---|---|---|
Next Message | Gudmundur Johannesson | 2013-09-04 08:34:04 | Re: Generic function for partitioning function? |
Previous Message | Adrian Klaver | 2013-09-04 02:12:56 | Re: store multiple rows with the SELECT INTO statement |