From: | Simon Riggs <simon(at)2ndquadrant(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>, Dave Page <dpage(at)pgadmin(dot)org> |
Subject: | Re: Rollback in Postgres |
Date: | 2008-07-14 20:20:38 |
Message-ID: | 1216066838.19656.11.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Mon, 2008-07-14 at 21:59 +0200, Kaare Rasmussen wrote:
> > I just lost a months worth of stats data myself, so join the club. It
> > wasn't critical data, but it would have been nice to have kept
> > around...
>
> 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.
>
> The idea is of course to be able to retrieve rows that really are deleted, but
> are still on disk as non-vacuumed or vacuumed and not removed completely. And
> it would also take a 2. stage vacuumer to keep the storage within its limits.
I've got the design all worked out for this.
The "only" thing we need is a VACUUM that will remove unseen data from
within the middle of the sum-of-all-snapshots, if there is a gap. At the
moment we never remove rows beyond global xmin, but we could iff the
transactions at xmin promise never to update data. That should go on the
TODO list as a precursor. Some discussion required :-)
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Kaare Rasmussen | 2008-07-14 20:34:33 | Re: Rollback in Postgres |
Previous Message | Alvaro Herrera | 2008-07-14 20:10:44 | Re: Rollback in Postgres |