| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Exclusion Constraints on Arrays? |
| Date: | 2012-05-23 17:35:24 |
| Message-ID: | CA+TgmoakBdj-i8DfXJKndpz=Jhut2ApWWTzVpcDSqHk3gsYidw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 23, 2012 at 1:34 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> On 13 May 2012 23:45, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Hmm, it looks like GIN can't support exclusive constraints because
>> amgettuple support is required, and unfortunately that got remove for
>> GIN in this commit:
>>
>> commit ff301d6e690bb5581502ea3d8591a1600fd87acc
>
> That seems very unfortunate, given that the 9.0 release notes say:
>
> "Exclusion constraints generalize uniqueness constraints by allowing
> arbitrary comparison operators, not just equality....This is useful
> for time periods and other ranges, as well as arrays."
I objected to it at the time, but lost the argument.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2012-05-23 17:38:33 | Re: Exclusion Constraints on Arrays? |
| Previous Message | Peter Geoghegan | 2012-05-23 17:34:01 | Re: Exclusion Constraints on Arrays? |