Exclusion constraint generates: ERROR: operator &&(anyrange,anyrange) is not a member of operator family "range_ops"
An EXCLUSION constraint with &amp;&amp; (Overlaps) needs to be GIST or SP-GIST because the default index is btree and its operator class does not support &amp;&amp; (Overlaps). From the docs on Interfacing Extensions To Indexes


  GiST indexes are more flexible: they do not have a fixed set of strategies at all. Instead, the “consistency” support routine of each particular GiST operator class interprets the strategy numbers however it likes. As an example, several of the built-in GiST index operator classes index two-dimensional geometric objects, providing the “R-tree” strategies shown in Table 37.4. Four of these are true two-dimensional tests (overlaps, same, contains, contained by); four of them consider only the X direction; and the other four provide the same tests in the Y direction.


You can use the GIST index on an exclusion constraint with,

CREATE TABLE foo (
  a tsrange,
  EXCLUDE USING GIST (a WITH &amp;&amp;)
);


The operator class


btree supports only &lt;, &lt;=, =, &gt;, &gt;=
gist and sp-gist support far more. And, gin may also one day support being used in an EXCLUSION constraint.


So long as the default GIST operator class is properly defaulted for the type you're using it should work: it's not for inet and cidr

See also,


Why does a CIDR or INET index require me to specify the index's Operator Class?