Re: pg_xlog on separate drive

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Travis Whitton" <tinymountain(at)gmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: pg_xlog on separate drive
Date: 2006-11-30 16:45:09
Message-ID: 14248.1164905109@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

"Travis Whitton" <tinymountain(at)gmail(dot)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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Matthew T. O'Connor 2006-11-30 18:08:55 Re: Autovaccum
Previous Message Jeff Herrin 2006-11-30 16:02:20 Re: consistent random order