Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 2C86E63344F
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 11 Feb 2010 19:00:51 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 53740-05 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 11 Feb 2010 23:00:25 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99])
	by mail.postgresql.org (Postfix) with ESMTP id 1A4946325FC
	for <pgsql-admin@postgresql.org>; Thu, 11 Feb 2010 19:00:39 -0400 (AST)
Received: from Courts-MTA by gw.wicourts.gov
	with Novell_GroupWise; Thu, 11 Feb 2010 17:00:38 -0600
Message-Id: <4B7437B1020000250002F1FD@gw.wicourts.gov>
X-Mailer: Novell GroupWise Internet Agent 8.0.1 
Date: Thu, 11 Feb 2010 17:00:33 -0600
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Albert Shih" <Albert.Shih@obspm.fr>,<pgsql-admin@postgresql.org>
Subject: Re: How to manage WAL
References: <20100211223245.GA13434@obspm.fr>
In-Reply-To: <20100211223245.GA13434@obspm.fr>
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-Spam-Status: No, hits=-1.539 tagged_above=-10 required=5 tests=AWL=-0.799,
	BAYES_20=-0.74
X-Spam-Level: 
X-Archive-Number: 201002/102
X-Sequence-Number: 33705

Albert Shih <Albert.Shih@obspm.fr> wrote:
 
> I would like to known what's best way to manage the WAL.
 
You should design a policy which meets your particular needs.  We
keep two PITR base backups and all the WAL files from before the
start of the first (based on the information in the backup file)
through current.  We also save monthly archival PITR base backups
with just the WAL files needed to restore them (again, based on the
backup files).  Your needs may be different.
 
-Kevin