| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | KES <kes-kes(at)yandex(dot)ru> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Typo in doc or wrong EXCLUDE implementation |
| Date: | 2018-08-08 13:00:40 |
| Message-ID: | 20180808130040.GA2611@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-08 13:51:28 | Re: Typo in doc or wrong EXCLUDE implementation |
| Previous Message | KES | 2018-08-08 10:55:53 | Re: Typo in doc or wrong EXCLUDE implementation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-08-08 13:36:08 | Re: Negotiating the SCRAM channel binding type |
| Previous Message | Tomas Vondra | 2018-08-08 12:39:54 | Re: [PATCH] Improve geometric types |