Re: How to allocate 8 disks

From: Shane Ambler <pgsql(at)Sheeky(dot)Biz>
To: Ivan Voras <ivoras(at)geri(dot)cc(dot)fer(dot)hr>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: How to allocate 8 disks
Date: 2008-03-04 15:04:32
Message-ID: 47CD6500.9030802@Sheeky.Biz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Ivan Voras wrote:
> Joshua D. Drake wrote:
>
>> This scares me... You lose WAL you are a goner. Combine your OS and
>> WAL into a RAID 1.
>
> Can someone elaborate on this? From the WAL concept and documentation at
> http://www.postgresql.org/docs/8.3/interactive/wal-intro.html I'd say
> the only data that should be lost are the transactions currently in the
> log but not yet transferred to permanent storage (database files proper).
>

The log records what changes are made to your data files before the data
files are changed. (and gets flushed to disk before the data files are
changed)

In the event of power loss right in the middle of the data files being
updated for a transaction, when power is restored, how do we know what
changes were made to which data files and which changes are incomplete?

Without the log files there is no way to be sure your data files are not
full of "half done transactions"

Chances are that 90% of the time everything is fine but without the log
files how do you check that your data files are as they should be.
(or do you expect to restore from backup after any power outs?)

Keeping them on a raid 1 gives you a level of redundancy to get you past
hardware failures that happen at the wrong time. (as they all do)

--

Shane Ambler
pgSQL (at) Sheeky (dot) Biz

Get Sheeky @ http://Sheeky.Biz

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Theo Kramer 2008-03-04 15:43:00 PostgreSQL performance on a virtual host
Previous Message Chris Kratz 2008-03-04 14:42:49 Ramifications of turning off Nested Loops for slow queries