Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL - Mailing list pgsql-general

From Jason L. Buberel
Subject Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL
Date
Msg-id 4688FB9B.3000808@buberel.org
Whole thread Raw
In response to Re: recovery_target_time ignored or recovery alwaysrecovers to end of WAL  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-general
Simon,

Thanks for the tip. I had assumed that so long as I set
'recovery_target_time' to a value that occurred before the 'fatal
commit' and set the 'inclusive' flag to false that I would be able to
return to just before the deletion occurred.

I'll play with it a bit more and see. I just want to know what to do in
the future should a real emergency like this occur.

Thanks,
jason

Simon Riggs wrote:
> On Sun, 2007-07-01 at 21:41 -0700, Jason L. Buberel wrote:
>
> Your example transactions are so large that going back 15 minutes is not
> enough. You'll need to go back further.
>
> recovery_target_time can only stop on a COMMIT or ABORT record. This is
> because it makes no sense to recover half a transaction, only whole
> transactions have meaning for recovery. So if the transactions are very
> large, you need to go back further.
>
>

pgsql-general by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: importing limited set of rows/tuples
Next
From: Michael Fuhr
Date:
Subject: Re: shmctl EIDRM preventing startup