From: Craig Ringer <ringerc@ringerc.id.au>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: mbroers@gmail.com
Cc: pgsql-admin@postgresql.org
Subject: Re: starting postgres with an empty px_xlog folder
Date: Sun, 24 Jun 2012 15:15:40 +0800
Message-ID: <4FE6BE9C.7000303@ringerc.id.au> (raw)
In-Reply-To: <4FE5D68A0200002500048A32@gw.wicourts.gov>
References: <4FE5D68A0200002500048A32@gw.wicourts.gov>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ringerc@ringerc.id.au, Kevin.Grittner@wicourts.gov, mbroers@gmail.com
Subject: Re: starting postgres with an empty px_xlog folder
In-Reply-To: <4FE6BE9C.7000303@ringerc.id.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox