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: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-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 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

2017-03-01 10:56 GMT+01:00 Peter Moser <pitiz...@gmail.com>: > 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 wi

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 <jim.na...@bluetreble.com>: > 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-t

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 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

2017-01-18 3:57 GMT+01:00 Peter Eisentraut <peter.eisentr...@2ndquadrant.com>: > > 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.

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

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 <pitiz...@gmail.com <mailto:pitiz...@gmail.com>> wrote: We decided to

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 <pitiz...@gmail.com <mailto:pitiz...@gmail.com>> wrote: We decided to follow your recommendation and add the patch to the commitfest. Path is not applying properly to HEAD. Move

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] Development with Eclipse - Wrong error messages in IDE

On 05.02.2016 um 18:40 Jason Petersen wrote: On Feb 3, 2016, at 2:38 AM, Peter Moser <pitiz...@gmail.com> wrote: Does anyone had similar problems? Do I have to configure Eclipse to understand the PG_RMGR macro or is there another possibility to teach Eclipse these macros? Hi, I just

Re: [HACKERS] Development with Eclipse - Wrong error messages in IDE

Peter Moser wrote: I have some strange error message inside Eclipse, that some symbols cannot be found. I work with version 9.6 currently. For instance, Symbol 'RM_HEAP_ID' could not be resolved src/backend/access/heap/heapam.c It affects all occurrences of symbols that are defined in src

[HACKERS] Development with Eclipse - Wrong error messages in IDE

Good morning hackers, I have some strange error message inside Eclipse, that some symbols cannot be found. I work with version 9.6 currently. For instance, Symbol 'RM_HEAP_ID' could not be resolved src/backend/access/heap/heapam.c It affects all occurrences of symbols that are defined in

Re: [HACKERS] Creating unique or "internal-use-only" column names (ColumnRef)

Am 07.09.2015 um 16:40 schrieb Tom Lane: Andrew Dunstan writes: On 09/07/2015 09:28 AM, Alvaro Herrera wrote: This seems pretty much the same as a junk attribute, if I understand you correctly. I suggest given a look at how those work. Is that actually documented

[HACKERS] Creating unique or "internal-use-only" column names (ColumnRef)

Good afternoon, is it possible to create unique column names or to give column names inside the parser phase that do not interfer with the outside world, i.e. with column names from tables or aliases given by the user. Some short background: I created my own from-clause-item, that gets

Re: [HACKERS] How to compare different datums within from a tuple?

Am 11.08.2015 um 21:03 schrieb Peter Eisentraut: On 8/10/15 12:36 PM, Peter Moser wrote: Can someone tell me, how I can compare two datum fields, when I do not know the data type in advance inside an executor function? For example, x less than y where x and y are of various types that form

Re: [HACKERS] How to compare different datums within from a tuple?

Am 11.08.2015 um 13:41 schrieb Anastasia Lubennikova: Can someone tell me, how I can compare two datum fields, when I do not know the data type in advance inside an executor function? In a nutshell, there is no way to compare Datums. Datum is an abstact data type. It's the backend

[HACKERS] How to compare different datums within from a tuple?

Hello, I try to write my first patch. It is too early to tell more about it, but I am just fiddling around with some prototypes. Can someone tell me, how I can compare two datum fields, when I do not know the data type in advance inside an executor function? For example, x less than y where