Message-ID: <4FE6BE9C.7000303@ringerc.id.au>
Date: Sun, 24 Jun 2012 15:15:40 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
CC: mbroers@gmail.com, pgsql-admin@postgresql.org
Subject: Re: starting postgres with an empty px_xlog folder
References: <4FE5D68A0200002500048A32@gw.wicourts.gov>
In-Reply-To: <4FE5D68A0200002500048A32@gw.wicourts.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 06/24/2012 03:45 AM, Kevin Grittner wrote:
> As previously stated, make sure you understand how this happened, so
> you can make sure it doesn't happen again.  The contents of the
> pg_xlog directory are an integral part of your database cluster.

People not backing up pg_xlog, deleting its contents, etc happens often 
enough that I wonder if it should have a prominent 00_README or 
00_WARNING_DONT_DELETE file created by initdb - or simply be renamed to 
something scarier like "base_txrecords".

The annoyance of a readme is that it'd need translation.

People are used to logs being disposable. Anyone who's been responsible 
for a database should ideally know better than to assume that 
*transation* logs are disposable, but everyone has to learn sometime, 
and not everybody does so by reading TFM (unfortunately).

--
Craig Ringer