| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kaare Rasmussen <kaare(at)jasonic(dot)dk> |
| Cc: | pgsql-sql(at)postgresql(dot)org, Richard Broersma <richard(dot)broersma(at)gmail(dot)com>, 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>, Dave Page <dpage(at)pgadmin(dot)org> |
| Subject: | Re: Rollback in Postgres |
| Date: | 2008-07-14 21:09:36 |
| Message-ID: | 1216069776.19656.20.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, 2008-07-14 at 22:38 +0200, Kaare Rasmussen wrote:
> > 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.
>
> Isn't this exactly what Alvaro describes? The time travel feature that was
> removed because it made Postgres too slow to use in production?
Similar. Performance is the issue to be solved with row removal, yes.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-15 01:18:04 | Re: Rollback in Postgres |
| Previous Message | Alvaro Herrera | 2008-07-14 20:54:54 | Re: Rollback in Postgres |