| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Aaron <aaron(at)chasingnuts(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: iSCSI SAN Suggestions |
| Date: | 2009-03-06 21:51:45 |
| Message-ID: | dcc563d10903061351h33320441wb45996077fbd1f51@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 6, 2009 at 6:47 AM, Aaron <aaron(at)chasingnuts(dot)com> wrote:
> We are facing an immediate need to refresh and expand some of our
> iSCSI storage we are running our PostgreSQL instance on. I am open to
> just about anything but I wondered if this group would have any
> suggestions. One item that is a bit unique to our situation, I am not
> in the need of staggering performance so much as I am in the need for
> very cost effective large mounts of storage. For more details on what
> I am doing: http://www.slideshare.net/AaronThul/this-is-your-postgresql-on-drugs
I have no direct experience with this, but would be interested in what
turns up on the mailing list.
Also, bump.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2009-03-06 22:24:16 | Log SQL code before executing it |
| Previous Message | Scott Marlowe | 2009-03-06 21:39:09 | Re: Maximum transaction rate |