From: Travis Whitton <tinymountain@gmail.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_xlog on separate drive
Date: Mon, 4 Dec 2006 09:04:57 -0500
Message-ID: <cf9b4f3e0612040604h320c2d87maa33e209545b74d3@mail.gmail.com> (raw)
In-Reply-To: <4573FEE0.2010406@logix-tt.com>
References: <cf9b4f3e0611300750o29aa04d0if2a44e26252cfddd@mail.gmail.com>
<4573FEE0.2010406@logix-tt.com>
Thanks for the replies guys. I think I may be ok in my case though because
I'll be importing data as a single daily batch from raw data. I'll be taking
nightly backups, and in the event of a crash, I can simply restore from a
recent backup and then reimport the raw data. I can now see why losing
pg_xlog would be a big problem if I were inserting and updating data
continuously throughout the day though.
Thanks,
Travis
On 12/4/06, Markus Schaber <schabi@logix-tt.com> wrote:
>
> Hi, Travis,
>
> Travis Whitton wrote:
> > 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.
>
> The problem is that you risk inconsistency at data and structural level.
>
> When the server crashes, it might happen that some pages in the data
> files are written only partially (because most disks have a much smaller
> blocksize than the PostgreSQL page size (which is 8k by default)).
>
> Now, when the server cannot reply the WAL log, those half-written pages
> will not be repaired, and your data may be inconsistent at a very low
> sematic level (duplicate rows, missing rows, broken rows, backend
> crashes etc.) with no way to repair.
>
> HTH,
> Markus
> --
> Markus Schaber | Logical Tracking&Tracing International AG
> Dipl. Inf. | Software Development GIS
>
> Fight against software patents in Europe! www.ffii.org
> www.nosoftwarepatents.org
>
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: tinymountain@gmail.com, schabi@logix-tt.com
Subject: Re: pg_xlog on separate drive
In-Reply-To: <cf9b4f3e0612040604h320c2d87maa33e209545b74d3@mail.gmail.com>
* 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