From: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: planned recovery from a certain transaction |
Date: | 2009-06-25 16:11:07 |
Message-ID: | 200906250911.07725@hal.medialogik.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 25 June 2009, "Chris Spotts" <rfusca(at)gmail(dot)com> wrote:
> The transaction itself works flawlessly, but every once and awhile the
> data the it uploads from comes in flawed and we have to find a way to
> reset it. This reset involves restoring a backup that was taken right
> before the proc started. If we had the xid of the long running
> transaction, is there a better way to reset it right before that
> transaction happened? Restoring the backup is a lengthy process because
> several of the tables that are affected are rather large.
>
PITR would permit you to restore the database to a point in time or a
transaction ID. You could probably do something with filesystem snapshots
to minimize backup/restore time for it.
--
WARNING: Do not look into laser with remaining eye.
From | Date | Subject | |
---|---|---|---|
Next Message | Hartman, Matthew | 2009-06-25 16:17:54 | Re: Vacuum on the database versus individual tables. |
Previous Message | Merlin Moncure | 2009-06-25 16:09:59 | Re: Vacuum on the database versus individual tables. |