Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 18C0D64FCE3
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 18 Dec 2008 18:19:50 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 24122-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 18 Dec 2008 18:19:46 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99])
	by mail.postgresql.org (Postfix) with ESMTP id 4BE5064FC42
	for <pgsql-admin@postgresql.org>; Thu, 18 Dec 2008 18:19:45 -0400 (AST)
Received: from Courts-MTA by gwmta.wicourts.gov
	with Novell_GroupWise; Thu, 18 Dec 2008 16:19:43 -0600
Message-Id: <494A7819.EE98.0025.0@wicourts.gov>
X-Mailer: Novell GroupWise Internet Agent 7.0.3 
Date: Thu, 18 Dec 2008 16:19:38 -0600
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Mark Steben" <msteben@autorevenue.com>,
	<pgsql-admin@postgresql.org>
Subject: Re: Warm Standby - log shipping
References: <D52D639EA1DC422DA3807EB17AF72239@dei26g028534>
In-Reply-To: <D52D639EA1DC422DA3807EB17AF72239@dei26g028534>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200812/151
X-Sequence-Number: 30984

>>> "Mark Steben" <msteben@autorevenue.com> wrote: 
 
> We are at postgresql 8.2.5
 
You really should update to 8.2.11 or consider going to 8.3.5.
 
http://www.postgresql.org/support/versioning
 
> We plan on using the Norfolk server not so much as a recovery
failover but
> as a replicated database
> To run reports and establish a data warehousing environment.  As such
the
> plan is to run  the 
> Standby in recovery state for the majority of the day, then
'complete'
> recovery there, bring it
> Online, perform our reporting and data warehousing functions (in
read-only
> mode of course),
> Then bring it back into recovery mode, letting the updates catch up
for the
> 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
postgres
> cannot find a valid checkpoint to restart.  What is the best way to
remedy
> this situation?  Pg_resetxlog perhaps?
 
I'd get a fresh base backup from which to start.
 
-Kevin