"Jason L. Buberel" <[EMAIL PROTECTED]> writes:
> Instead, in order to achieve my goal I would have to restore to that
> backup, and rely on the contents of the archive_logs to have the
> recovery process return me to the selected xid PITR.
Correct.
> So is there any way to 'trick' or force the server to forget what it
> thinks 'now' is and instead to step back to the selected xid and make
> that the new version of 'now'?
No. As an example, would you expect such a trick to reverse the effects
of a DROP TABLE? Or even just a single DELETE? That would mean we
could *never* free any storage.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
