From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Paul Howells <paul(dot)steven(dot)howells(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: SQL:2011 Valid-Time Support |
Date: | 2018-05-08 16:13:18 |
Message-ID: | 7f0286bd-cf68-d698-e14b-e283aa6ebd00@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/8/18 11:31, Tom Lane wrote:
> Paul Howells <paul(dot)steven(dot)howells(at)gmail(dot)com> writes:
>> Has there been or is there any current effort to implement SQL:2011
>> valid-time support in Postgres?
>
> Searching the archives, I can only find "valid-time" appearing in these
> threads related to temporal query processing:
>
> https://www.postgresql.org/message-id/flat/200702100020.28893.wt%40penguintechs.org
That looks like a pre-standardization variant of the same idea.
I think those are operators that work on top of having the valid-time
available, but don't do anything about making that time available.
> Anyway, if it's in the standard, then at least in principle we're open
> to it. There'd probably be some questions about the amount of added
> complexity and whether the feature is worth supporting. I'd suggest
> trying to get some community buy-in by circulating a design document
> on -hackers before you write any code.
I think there is some interest, so it's worth proceeding like that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-05-08 16:16:48 | Re: perlcritic and perltidy |
Previous Message | Teodor Sigaev | 2018-05-08 15:51:59 | Re: Cast jsonb to numeric, int, float, bool |