Re: EXLCUDE constraints and Hash indexes

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: EXLCUDE constraints and Hash indexes
Date: 2016-08-17 13:12:09
Message-ID: 87inuzk0bp.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Jeff" == Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:

Jeff> From: https://www.postgresql.org/docs/9.4/static/sql-createtable.html

Jeff> "The access method must support amgettuple (see Chapter 55); at
Jeff> present this means GIN cannot be used. Although it's allowed, there is
Jeff> little point in using B-tree or hash indexes with an exclusion
Jeff> constraint, because this does nothing that an ordinary unique
Jeff> constraint doesn't do better. So in practice the access method will
Jeff> always be GiST or SP-GiST."

I also recently found a case where using btree exclusion constraints was
useful: a unique index on an expression can't be marked deferrable, but
the equivalent exclusion constraint can be.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-08-17 13:27:22 Re: patch proposal
Previous Message Robert Haas 2016-08-17 13:01:23 Re: Surprising behaviour of \set AUTOCOMMIT ON