From: Gregory Stark <stark@enterprisedb.com>
To: Hannes Dorbath <light@theendofthetunnel.de>
Cc: Joseph <spmok2@canada.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950
Date: Sat, 14 Jul 2007 10:57:55 +0100
Message-ID: <87tzs7b93w.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <46988951.9050108@theendofthetunnel.de>
References: <1184357777.135345.38110@n60g2000hse.googlegroups.com>
<46988951.9050108@theendofthetunnel.de>
"Hannes Dorbath" <light@theendofthetunnel.de> writes:
> From the DELL site it seems this `PERC 5/i' on board controller
> (assuming that's what you have) doesn't even have a BBU. If you don't
> plan to post here in a few weeks again about data corruption, go out and
> shop a serious controller.
This is a bit of a strange comment. A BBU will improve performance but
Postgres doesn't require one to guarantee data integrity.
If your drives have write caching disabled (ie write-through) and your
controller does write-through caching and you leave fsync=on and
full_page_writes=on which is the default then you shouldn't have any data
integrity issues.
Note that many drives, especially IDE drives ship with write caching enabled
(ie, write-back).
And without a BBU many people are tempted to set fsync=off which improves
performance at the cost of data loss on a system crash or power failure. With
a BBU there's no advantage to fsync=off so that temptation to risk data loss
is removed.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
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-performance@postgresql.org
Cc: stark@enterprisedb.com, light@theendofthetunnel.de, spmok2@canada.com
Subject: Re: FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950
In-Reply-To: <87tzs7b93w.fsf@oxford.xeocode.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