| From: | Peter Moser <pitiz29a(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Johann Gamper <gamper(at)inf(dot)unibz(dot)it>, Michael Böhlen <boehlen(at)ifi(dot)uzh(dot)ch>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Anton Dignös <anton(dot)dignoes(at)unibz(dot)it> |
| Subject: | Re: [PROPOSAL] Temporal query processing with range types |
| Date: | 2017-09-22 08:51:12 |
| Message-ID: | CAHO0eLat6suO1qcefwsgPPcL=Gr5MUM2SaFieVRbMF_RgN1nQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2017-09-22 10:21 GMT+02:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Currently Postgres has zero support for SQL:2011 temporal tables. Isn't
> better start with already standard features than appends some without
> standard? The standard has some concept and if we start out of this concept,
> then the result will be far to standard probably.
We will focus for now on the Range Merge Join algorithm by Jeff Davis,
which implements a temporal join with overlap predicates.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2017-09-22 10:43:29 | Re: UPDATE of partition key |
| Previous Message | Andreas Karlsson | 2017-09-22 08:50:01 | Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it? |