Re: operator exclusion constraints

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: operator exclusion constraints
Date: 2009-11-06 19:13:53
Message-ID: 1257534833.28470.218.camel@monkey-cat.sm.truviso.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2009-11-06 at 14:05 -0500, Tom Lane wrote:
> BTW, where is the optional opclass name going to fit in? ("There
> isn't one" is not an acceptable answer.)

"expression" is actually an index_elem, which includes all of the
options including the opclass. I'll make that more clear.

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-11-06 19:22:03 Re: operator exclusion constraints
Previous Message Jeff Davis 2009-11-06 19:11:28 Re: operator exclusion constraints