From: | Steve Midgley <science(at)misuse(dot)org> |
---|---|
To: | Ravi Krishna <sravikrishna3(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: PG and Temporal |
Date: | 2015-06-01 17:25:29 |
Message-ID: | CAJexoSJX+LvKJPpXmMDwPuPE-xxx1nGcPNpKzcZB0gAJJRwtZA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, May 26, 2015 at 1:59 PM, Ravi Krishna <sravikrishna3(at)gmail(dot)com>
wrote:
> Hi,
>
> I am researching temporal (both system time and business time) in PG.
>
> I got the following hits:
>
> https://wiki.postgresql.org/wiki/SQL2011Temporal
>
> http://pgxn.org/dist/temporal_tables/
>
> Is there anything else I am missing.
>
>
>
I think there are a lot of theories as to how to make temporal table
systems work. It hugely depends on your requirements. That said, the data
warehouse community has built a kind of solution with dimension tables
representing time, and fact tables aligning to those dimensions via
relations. It makes certain temporal "grain size" problems much easier to
solve (and usually faster). Though using Pg's date extraction functions
I've gotten pretty amazing performance as well: basically creating
on-demand time dimensions as needed.. Read Ralph Kimball's work on data
warehousing for a good introduction.
This isn't the same as creating versioned tables per your references above
but I hope will be useful in your research..
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2015-06-01 18:02:34 | Re: PG and Temporal |
Previous Message | Shashwat Arghode | 2015-05-29 06:13:06 | Re: [SQL] Drop or disable or bypass "_return" rule on select on a view. |