From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Jeremy Finzel <finzelj(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Primary key gist index? |
Date: | 2018-03-14 13:33:34 |
Message-ID: | bcb9d38a-861a-cb89-97c7-3c606b43b5a7@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/14/2018 06:19 AM, Jeremy Finzel wrote:
> Hello! From all that I can tell, it is not possible using a btree_gist
> index as a primary key. If so, why not? I have a table with this gist
https://www.postgresql.org/docs/10/static/btree-gist.html
"In general, these operator classes will not outperform the equivalent
standard B-tree index methods, and they lack one major feature of the
standard B-tree code: the ability to enforce uniqueness."
> index which truly ought to be its primary key. as_of_date is of range
> date type:
>
> EXCLUDE USING gist (id WITH =, as_of_date WITH &&)
>
> Any direction here would be much appreciated.
>
> Right now, I am forced to create a redundant btree index UNIQUE, btree
> (id, lower(as_of_date)) in order to have a primary key on the table.
>
> Thanks!
> Jeremy
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | chris | 2018-03-14 14:51:33 | Re: JDBC connectivity issue |
Previous Message | Jeremy Finzel | 2018-03-14 13:19:49 | Primary key gist index? |