| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | KES <kes-kes(at)yandex(dot)ru> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql(at)j-davis(dot)com |
| Subject: | Re: Typo in doc or wrong EXCLUDE implementation |
| Date: | 2018-08-08 15:02:39 |
| Message-ID: | 20180808150239.6gp6vgisxcempyoh@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2018-Aug-08, 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.
I think what you're looking for is "inclusion constraints" from Jeff
Davis:
https://postgr.es/m/1423354088.12308.117.camel@jeff-desktop
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-08 15:57:17 | Re: dblink_error_message return value |
| Previous Message | Chris Travers | 2018-08-08 14:53:42 | Re: Release note trimming: another modest proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-08-08 15:11:30 | Re: Facility for detecting insecure object naming |
| Previous Message | Mark Dilger | 2018-08-08 14:51:27 | Re: Facility for detecting insecure object naming |