Earlier this evening I made the usual mistake someone makes at some
point in their lives - and dropped a database thinking I didn't need it,
then realised later I did.
So, because I have DDL statement logging turned on, I could find the
exact time/date it happened, and attempted to restore from
Andy Shellam (Mailing Lists) [EMAIL PROTECTED] writes:
(Note, after writing this, I tried restoring to a minute earlier (ie.
18:57:40) and still have the same problem.
The PITR recovery process in effect rolls forward until it finds
a transaction-commit record = the specified time. Now for
Thanks for the info Tom, too much data will have been entered into the
other databases in the cluster by now so I cannot give it another shot
on that server, plus all of yesterday's WAL logs will have been purged
by now by the daily backup routine.
Is it enough to simply have re-copied in the
Andy Shellam (Mailing Lists) [EMAIL PROTECTED] writes:
Is it enough to simply have re-copied in the base/xxx directory from the
base backup, after the PITR recovery had completed (obviously any
changes made to that database since the base backup won't have been
restored but thankfully it's
