From: Tom Lane <tgl@sss.pgh.pa.us>
To: Travis Whitton <tinymountain@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_xlog on separate drive
Date: Thu, 30 Nov 2006 11:45:09 -0500
Message-ID: <14248.1164905109@sss.pgh.pa.us> (raw)
In-Reply-To: <cf9b4f3e0611300750o29aa04d0if2a44e26252cfddd@mail.gmail.com>
References: <cf9b4f3e0611300750o29aa04d0if2a44e26252cfddd@mail.gmail.com>
"Travis Whitton" <tinymountain@gmail.com> writes:
> Hey guys, sorry if this is slightly OT for this list, but I figure it's a
> simple question. If I'm storing pg_xlog on a second non-redundant drive
> using the symlink method and the journal drive were to crash, how difficult
> is recovery? Will Postgresql simply be able to reinitialize the journal on a
> new drive and carry on, or is there more to it than that? I realize any
> pending transactions would be lost, but that's not a huge concern for me
> because everything I'm importing comes from raw data.
Losing xlog is pretty bad: there's a serious risk of data corruption, in
that transactions made since your last checkpoint may be only partially
applied. I wouldn't recommend a setup in which xlog is less redundant
than your main storage array.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, tinymountain@gmail.com
Subject: Re: pg_xlog on separate drive
In-Reply-To: <14248.1164905109@sss.pgh.pa.us>
* 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