| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Peter Moser <pitiz29a(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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-02-16 12:41:37 |
| Message-ID: | CA+TgmoZY=B4KGk7RyNN9E2RfQN2yt=ShDT12bQWwR-i4NoF=hQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 15, 2017 at 3:33 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> The description in the OP basically distinguishes between NORMALIZE and
> ALIGN in that ALIGN, as described above, affects an INTERSECTION on the two
> ranges - discarding the non-overlapping data - while NORMALIZE performs the
> alignment while also retaining the non-overlapping data.
Hmm. So is ALIGN like an inner join and NORMALIZE like a full outer
join? Couldn't you have left and right outer joins, too, like you
null-extend the parts of the lefthand range that don't match but throw
away parts of the righthand range that don't match?
Also, it sounds like all of this is intended to work with ranges that
are stored in different columns rather than with PostgreSQL's built-in
range types.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-02-16 12:49:59 | Re: SERIALIZABLE with parallel query |
| Previous Message | Rafia Sabih | 2017-02-16 12:17:57 | Re: Passing query string to workers |