>>> "Mark Steben" <msteben(at)autorevenue(dot)com> wrote:
> We are at postgresql 8.2.5
You really should update to 8.2.11 or consider going to 8.3.5.
> We plan on using the Norfolk server not so much as a recovery
> as a replicated database
> To run reports and establish a data warehousing environment. As such
> plan is to run the
> Standby in recovery state for the majority of the day, then
> recovery there, bring it
> Online, perform our reporting and data warehousing functions (in
> mode of course),
> Then bring it back into recovery mode, letting the updates catch up
> next days processing.
> My questions are:
> 1. Is this a proper usage of log shipping?
Once you complete recovery you don't have a good way back, short of
getting a new base backup. If you have space, you could stop the
replica server without leaving recovery state, do a copy of the
cluster to another directory, restart your replica, start the copied
cluster's server, complete recovery, and start running your reports.
> 3. I am currently in a state where a log got partially copied and
> cannot find a valid checkpoint to restart. What is the best way to
> this situation? Pg_resetxlog perhaps?
I'd get a fresh base backup from which to start.
In response to
pgsql-admin by date
|Next:||From: Joshua D. Drake||Date: 2008-12-18 22:20:35|
|Subject: Re: Warm Standby - log shipping|
|Previous:||From: Mark Steben||Date: 2008-12-18 21:43:10|
|Subject: Warm Standby - log shipping|