| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | david(at)lang(dot)hm |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: What is the best way to storage music files in Postgresql |
| Date: | 2008-03-18 22:52:32 |
| Message-ID: | 47E047B0.3090100@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
david(at)lang(dot)hm wrote:
> you can? I've never seen a raid 5 setup with more then a single parity
> dirve (or even the option of having more then one drives worth of
> redundancy). you can have hot-spare drives, but thats a different thing.
>
With RAID 4, where the "parity drives" are in fact dedicated to parity
information, the controller could just store the parity data mirrored on
more than one drive. Unfortunately write performance on RAID 4 is
absolutely horrible, and a second or third parity disk would not help
with that.
I suppose there's nothing stopping a controller adding a second disk's
worth of duplicate parity information when striping a four or more disk
RAID 5 array, but I thought that's basically what RAID 6 was.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2008-03-18 23:09:59 | Re: What is the best way to storage music files in Postgresql |
| Previous Message | Craig Ringer | 2008-03-18 22:44:57 | Re: What is the best way to storage music files in Postgresql |