Re: Asking for assistance in determining storage requirements - Mailing list pgsql-general

From Alan McKay
Subject Re: Asking for assistance in determining storage requirements
Date
Msg-id 844129e80907160713u784e9fb2q87664c64cb6ebc5c@mail.gmail.com
Whole thread Raw
In response to Asking for assistance in determining storage requirements  (Chris Barnes <compuguruchrisbarnes@hotmail.com>)
List pgsql-general
No other takers on this one?

I'm wondering what exactly "direct attached storage" entails?

At PG Con I heard a lot about using only direct-attached storage, and not a SAN.
Are there numbers to back this up?

Does fibre-channel count as direct-attached storage?   I'm thinking it would.

What exactly is recommended against?  Any strorage that is TCP/IP based?

On Thu, Jul 9, 2009 at 11:15 AM, Chris
Barnes<compuguruchrisbarnes@hotmail.com> wrote:
> You assistance is appreciated.
>
>
> I have question regarding disk storage for postgres servers
>
>
>
> We are thinking long term about scalable storage and performance and would
> like some advise
> or feedback about what other people are using.
>
>
>
> We would like to get as much performance from our file systems as possible.
>
>
>
> We use ibm 3650 quad processor with onboard SAS controller ( 3GB/Sec) with
> 15,000rpm drives.
>
> We use raid 1 for the centos operating system and the wal archive logs.
>
> The postgres database is on 5 drives configured as raid 5 with a global hot
> spare.
>
>
>
> We are curious about using SAN with fiber channel hba and if anyone else
> uses this technology.
>
> We would also like to know if people have preference to the level of raid
> with/out striping.
>
> Sincerely,
>
> Chris Barnes
> Recognia Inc.
> Senior DBA
>
> ________________________________
> Attention all humans. We are your photos. Free us.



--
“Don't eat anything you've ever seen advertised on TV”
         - Michael Pollan, author of "In Defense of Food"

pgsql-general by date:

Previous
From: "Roseller A. Romanos"
Date:
Subject: Please help
Next
From: Florian Weimer
Date:
Subject: Re: Working around spurious unique constraint errors due to SERIALIZABLE bug