| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-28 00:00:02 |
| Message-ID: | 20040428000002.GV41429@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Another idea would be to provide some means to roll a database forwards
and backwards. If you're doing a recovery because you did something like
an accidental UPDATE SET field = blah without a where clause, what you
really care about is going up to the point right before that update. If
there's a log viewer with enough detail, that would suffice; otherwise
you'd need to test for some specific condition.
Of course timestamps would still be useful in this scenario since they
can get you close to the transaction in question.
--
Jim C. Nasby, Database Consultant jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-04-28 00:00:03 | Re: Usability, MySQL, Postgresql.org, gborg, contrib, |
| Previous Message | Jim C. Nasby | 2004-04-27 23:45:33 | Re: Usability, MySQL, Postgresql.org, gborg, contrib, |