| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | mbroers(at)gmail(dot)com, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: starting postgres with an empty px_xlog folder |
| Date: | 2012-06-24 07:15:40 |
| Message-ID: | 4FE6BE9C.7000303@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Bishop | 2012-06-24 08:15:14 | Re: starting postgres with an empty px_xlog folder |
| Previous Message | Craig Ringer | 2012-06-24 07:01:53 | Re: terminating autovacuum process due to administrator command |