Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Fri, Oct 6, 2017 at 3:22 PM, Mike Rylander wrote: > I've also been following this feature with great interest, and would > definitely throw whatever tiny weight I have, sitting out here in the > the peanut gallery, behind accepting the ALIGN and NORMALIZE syntax. > I

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Fri, Oct 6, 2017 at 1:22 PM, Paul A Jungwirth wrote: > On Fri, Jul 22, 2016 at 4:15 AM, Anton Dignös wrote: >> We would like to contribute to PostgreSQL a solution that supports the query >> processing of "at each time point". The basic

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Fri, Jul 22, 2016 at 4:15 AM, Anton Dignös wrote: > We would like to contribute to PostgreSQL a solution that supports the query > processing of "at each time point". The basic idea is to offer two new > operators, NORMALIZE and ALIGN, whose purpose is to adjust (or

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-22 10:21 GMT+02:00 Pavel Stehule : > 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, >

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-22 10:15 GMT+02:00 Peter Moser : > 2017-09-22 10:06 GMT+02:00 Pavel Stehule : > > ANSI SQL 2011 has temporal data support > > > > https://www.slideshare.net/CraigBaumunk/temporal- > extensions-tosql20112012010438 > > As operations it only

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-22 10:06 GMT+02:00 Pavel Stehule : > ANSI SQL 2011 has temporal data support > > https://www.slideshare.net/CraigBaumunk/temporal-extensions-tosql20112012010438 As operations it only supports temporal inner joins using the overlap predicate. Temporal aggregation,

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-22 9:59 GMT+02:00 Peter Moser : > 2017-09-12 16:33 GMT+02:00 Simon Riggs : > > PostgreSQL tries really very hard to implement the SQL Standard and > > just the standard. ISTM that the feedback you should have been given > > is that this is very

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-09-12 16:33 GMT+02:00 Simon Riggs : > PostgreSQL tries really very hard to implement the SQL Standard and > just the standard. ISTM that the feedback you should have been given > is that this is very interesting but will not be committed in its > current form; I am

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 30 March 2017 at 13:11, Peter Moser wrote: > 2017-03-01 10:56 GMT+01:00 Peter Moser : >> A similar walkthrough for ALIGN will follow soon. >> >> We are thankful for any suggestion or ideas, to be used to write a >> good SGML documentation. > > The

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Tue, Aug 1, 2017 at 12:53 AM, Peter Moser wrote: > On 06.04.2017 01:24, Andres Freund wrote: >> >> Unfortunately I don't think this patch has received sufficient design >> and implementation to consider merging it into v10. As code freeze is >> in two days, I think we'll

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 06.04.2017 01:24, Andres Freund wrote: Unfortunately I don't think this patch has received sufficient design and implementation to consider merging it into v10. As code freeze is in two days, I think we'll have to move this to the next commitfest. We rebased our patch on top of commit

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

Hi, On 2017-03-30 14:11:28 +0200, Peter Moser wrote: > 2017-03-01 10:56 GMT+01:00 Peter Moser : > > A similar walkthrough for ALIGN will follow soon. > > > > We are thankful for any suggestion or ideas, to be used to write a > > good SGML documentation. > > The attached

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-03-01 10:56 GMT+01:00 Peter Moser : > A similar walkthrough for ALIGN will follow soon. > > We are thankful for any suggestion or ideas, to be used to write a > good SGML documentation. The attached README explains the ALIGN operation step-by-step with a TEMPORAL LEFT

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-02-15 20:24 GMT+01:00 Robert Haas : > There's no documentation in this patch. I'm not sure you want to go > to the trouble of writing SGML documentation until this has been > reviewed enough that it has a real chance of getting committed, but on > the other hand we're

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-02-24 21:25 GMT+01:00 Jim Nasby : > On 2/24/17 6:40 AM, Peter Moser wrote: >> >> Do you think it is better to remove the syntax for ranges expressed in >> different columns? > > > It's not that hard to construct a range type on-the-fly from 2 columns, so > (without

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 2/24/17 6:40 AM, Peter Moser wrote: Do you think it is better to remove the syntax for ranges expressed in different columns? It's not that hard to construct a range type on-the-fly from 2 columns, so (without having looked at the patch or really followed the thread) I would think the

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-02-22 19:43 GMT+01:00 Peter Eisentraut : > On 2/16/17 07:41, Robert Haas wrote: >> 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. > > Yeah, that

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 2/16/17 07:41, Robert Haas wrote: > 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. Yeah, that should certainly be changed. -- Peter Eisentraut

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Wed, Feb 15, 2017 at 9:33 PM, David G. Johnston wrote: > On Wed, Feb 15, 2017 at 12:24 PM, Robert Haas wrote: >> >> So it seems like an ALIGN or NORMALIZE option is kind of like a JOIN, >> except apparently there's no join type and the

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Wed, Feb 15, 2017 at 3:33 PM, David G. Johnston 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

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Wed, Feb 15, 2017 at 12:24 PM, Robert Haas wrote: > On Tue, Jan 24, 2017 at 4:32 AM, Peter Moser wrote: > >> Using common terms such as ALIGN and NORMALIZE for such a specific > >> functionality seems a bit wrong. > > > > Would ALIGN RANGES/RANGE

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Tue, Jan 24, 2017 at 4:32 AM, Peter Moser wrote: >> Using common terms such as ALIGN and NORMALIZE for such a specific >> functionality seems a bit wrong. > > Would ALIGN RANGES/RANGE ALIGN and NORMALIZE RANGES/RANGE NORMALIZE be better > options? We are also thankful for

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Tue, Jan 24, 2017 at 4:32 AM, Peter Moser wrote: > NORMALIZE: splits all the ranges of one relation according to all the range > boundaries of another (but possibly the same) relation whenever some equality > condition over some given attributes is satisfied. > > When the

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 2/2/17 12:43 PM, Peter Moser wrote: > Hereby, we used the following commands to create both patches: > git diff --no-prefix origin/master -- src/ ':!src/test/*' > > tpg_primitives_out_v4.patch > > git diff --no-prefix origin/master -- src/test/ > > tpg_primitives_out_tests_v2.patch > > We

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Tue, Jan 24, 2017 at 6:32 PM, Peter Moser wrote: > [reviews and discussions] The patch proposed has rotten. Please provide a rebase. By the way, I am having a hard time applying your patches with patch or any other methods... I am moving it to CF 2017-03 because of the

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

2017-01-18 3:57 GMT+01:00 Peter Eisentraut : > > On 1/13/17 9:22 AM, Peter Moser wrote: > > The goal of temporal aligners and normalizers is to split ranges to allow a > > reduction from temporal queries to their non-temporal counterparts. > > Splitting > > ranges

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 1/13/17 9:22 AM, Peter Moser wrote: > The goal of temporal aligners and normalizers is to split ranges to allow a > reduction from temporal queries to their non-temporal counterparts. > Splitting > ranges is necessary for temporal query processing. Temporal aligners and > normalizer may then be

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

> What this patch does is to add two new clauses for FROM-list items, > NORMALIZE and ALIGN, which reshuffle a set of ranges into a new list > that can then be aggregated more easily. From the original message: > > > For NORMALIZE the tuples' ranges need to be split into all sub-ranges > >

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

So I'm looking at this patch in the commit fest. I have only a general understanding of temporal query processing. What this patch does is to add two new clauses for FROM-list items, NORMALIZE and ALIGN, which reshuffle a set of ranges into a new list that can then be aggregated more easily.

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

Am 16.12.2016 um 07:17 schrieb David Fetter: On Wed, Dec 07, 2016 at 03:57:33PM +0100, Peter Moser wrote: Am 05.12.2016 um 06:11 schrieb Haribabu Kommi: On Tue, Oct 25, 2016 at 8:44 PM, Peter Moser > wrote: We decided to follow your

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Wed, Dec 07, 2016 at 03:57:33PM +0100, Peter Moser wrote: > Am 05.12.2016 um 06:11 schrieb Haribabu Kommi: > > > > > > On Tue, Oct 25, 2016 at 8:44 PM, Peter Moser > > wrote: > > > > > > We decided to follow your recommendation and add

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

Am 05.12.2016 um 06:11 schrieb Haribabu Kommi: On Tue, Oct 25, 2016 at 8:44 PM, Peter Moser > wrote: We decided to follow your recommendation and add the patch to the commitfest. Path is not applying properly to HEAD. Moved to next CF

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Tue, Oct 25, 2016 at 8:44 PM, Peter Moser wrote: > > We decided to follow your recommendation and add the patch to the > commitfest. > > Path is not applying properly to HEAD. Moved to next CF with "waiting on author" status. Regards, Hari Babu Fujitsu Australia

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On 27.07.2016 at 16:09 Robert Haas wrote: On Fri, Jul 22, 2016 at 7:15 AM, Anton Dignös wrote: We would like to contribute to PostgreSQL a solution that supports the query processing of "at each time point". The basic idea is to offer two new operators, NORMALIZE and

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Fri, Jul 22, 2016 at 7:15 AM, Anton Dignös wrote: > We would like to contribute to PostgreSQL a solution that supports the query > processing of "at each time point". The basic idea is to offer two new > operators, NORMALIZE and ALIGN, whose purpose is to adjust (or

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Sat, Jul 23, 2016 at 12:01 AM, David Fetter wrote: > On Fri, Jul 22, 2016 at 01:15:17PM +0200, Anton Dignös wrote: >> Hi hackers, >> >> we are a group of researches that work on temporal databases. Our >> main focus is the processing of data with time intervals, such as >>

Re: [HACKERS] [PROPOSAL] Temporal query processing with range types

On Fri, Jul 22, 2016 at 01:15:17PM +0200, Anton Dignös wrote: > Hi hackers, > > we are a group of researches that work on temporal databases. Our > main focus is the processing of data with time intervals, such as > the range types in PostgreSQL. Thanks for your hard work so far! [Explanation