Date: Wed, 8 Aug 2018 09:00:40 -0400
From: Bruce Momjian <bruce@momjian.us>
To: KES <kes-kes@yandex.ru>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Typo in doc or wrong EXCLUDE implementation
Message-ID: <20180808130040.GA2611@momjian.us>
References: <153121527691.1408.5686988620817799073@wrigleys.postgresql.org>
 <20180807173659.GD7297@momjian.us>
 <31616681533725753@sas1-d856b3d759c7.qloud-c.yandex.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <31616681533725753@sas1-d856b3d759c7.qloud-c.yandex.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

On Wed, Aug  8, 2018 at 01:55:53PM +0300, KES wrote:
> I do not know many internals and maybe wrong.
> 
> But from my point of view with my current knowledge. 
> If such exclusion constraint would be marked as UNIQUE we can use it for FK while implementing temporal/bi-temporal tables.
> 
> And this will be simplify relationing while implementing them.

Yes, it would work, but doing that only for equality would be surprising
to many people because exclusion constraints are more general than
equality comparisons.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +