From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: starting postgres with an empty px_xlog folder |
Date: | 2012-06-24 08:15:14 |
Message-ID: | CADmi=6OgD6177tjAhTjQ-XqKRKe12Lt15_kCm6gr04Z_p4CR6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, Jun 24, 2012 at 2:15 PM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
> 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".
This doesn't help when your backup skips them because the files exist
on another disk partition. Out of sight, out of mind.
If pg_basebackup defaulted to --xlog and its use was encouraged these
mistakes might be less common.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | wangqi | 2012-06-25 06:45:29 | a very slow SQL |
Previous Message | Craig Ringer | 2012-06-24 07:15:40 | Re: starting postgres with an empty px_xlog folder |