| From: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | "Kaare Rasmussen" <kaare(at)jasonic(dot)dk> |
| Cc: | pgsql-sql(at)postgresql(dot)org, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "samantha mahindrakar" <sam(dot)mahindrakar(at)gmail(dot)com>, "Lewis Cunningham" <lewisc(at)rocketmail(dot)com>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Dave Page" <dpage(at)pgadmin(dot)org> |
| Subject: | Re: Rollback in Postgres |
| Date: | 2008-07-14 20:06:56 |
| Message-ID: | 396486430807141306s3079bd25m2dd9f8b4f3a19232@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jul 14, 2008 at 12:59 PM, Kaare Rasmussen <kaare(at)jasonic(dot)dk> wrote:
> I also think there could be a TODO item in it. If vacuum instead of removing
> items, somehow stashed them away in a storage limited archive it would be
> possible to do a SELECT...AS OF TIMESTAMP.
This sounds a lot like the functionality that a temporal data model
would give you. In this model you never delete tuples from your
database, your only insert and update tuples that are valid for
specific periods of time.
If you want to contribute development time, I would check out
postgresql's temporal db project on PGfoundry. This project is just
getting started and could benefit from a lot of development help.
--
Regards,
Richard Broersma Jr.
Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-07-14 20:10:44 | Re: Rollback in Postgres |
| Previous Message | Kaare Rasmussen | 2008-07-14 19:59:01 | Re: Rollback in Postgres |