From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Hannes Dorbath" <light(at)theendofthetunnel(dot)de> |
Cc: | "Joseph" <spmok2(at)canada(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950 |
Date: | 2007-07-14 09:57:55 |
Message-ID: | 87tzs7b93w.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Hannes Dorbath" <light(at)theendofthetunnel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Hannes Dorbath | 2007-07-14 10:19:51 | Re: FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950 |
Previous Message | Steinar H. Gunderson | 2007-07-14 08:34:40 | Re: FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950 |