| From: | Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Subject: | Re: SQL:2011 PERIODS vs Postgres Ranges? |
| Date: | 2019-08-02 20:28:23 |
| Message-ID: | 156477770335.1401.7738145215865735767.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The patch does not work.
postgres=# CREATE TABLE foo (id int,r int4range, valid_at tsrange, CONSTRAINT bar_pk PRIMARY KEY (r, valid_at WITHOUT OVERLAPS));
CREATE TABLE
postgres=# CREATE TABLE bar (id int,r int4range, valid_at tsrange, CONSTRAINT bar_fk FOREIGN KEY (r, PERIOD valid_at) REFERENCES foo);
ERROR: cache lookup failed for type 0
The new status of this patch is: Waiting on Author
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-08-02 20:30:59 | Re: partition routing layering in nodeModifyTable.c |
| Previous Message | Tom Lane | 2019-08-02 20:21:07 | First draft of back-branch release notes is done |