| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: SQL:2011 PERIODS vs Postgres Ranges? |
| Date: | 2019-03-10 00:41:44 |
| Message-ID: | CA+renyWEv4uB9DkPhSSvqQcD40mxLwh1RGyZQsiqcwZVE0Y4WQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 5, 2019 at 12:35 AM David Steele <david(at)pgmasters(dot)net> wrote:
> I have marked this patch as targeting PG13 since it is clearly not
> material for PG12. I also added you as the patch author.
Thanks David! Targeting PG13 was my intention, so sorry if I messed up
the commitfest entry.
Here is a new patch rebased on top of master. My questions are inline
as TODO comments for whoever does the review. I'm pretty far along
with an add-on patch to create temporal *foreign* keys too, which I
think should be part of this same bundle of work. If anyone happens to
review the PK patch soon, it might help me avoid the same mistakes in
the FK work, but if not that's fine too. :-)
Yours,
Paul
| Attachment | Content-Type | Size |
|---|---|---|
| temporal_pks_v0003.patch | application/octet-stream | 28.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2019-03-10 04:49:26 | Re: Pluggable Storage - Andres's take |
| Previous Message | Tom Lane | 2019-03-09 22:14:25 | Re: Should we increase the default vacuum_cost_limit? |