On Fri, Mar 18, 2011 at 3:22 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> If recovery target is set to before its consistent, ie. before
> minRecoveryPoint, we should throw an error before recovery even starts. I'm
> not sure if we check that at the moment.
I don't see how you could check that anyway. How do you know where
you're going to see the given XID/timestamp/named restore point until
you actually get there?
> Not sure what to to do recovery target is beyond minRecoveryPoint and
> pause_at_recovery_target=true, but the server hasn't been opened for hot
> standby yet (because it hasn't seen a running-xacts record yet). I agree
> it's pretty useless and annoying to stop there.
I think the reasonable options are "enter normal running" and "shut down".
In any event, it sounds like someone needs to fix this, and I don't
know enough to do it. Can you or Fujii Masao do it?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
