Re: table spaces

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: sthomas(at)optionshouse(dot)com
Cc: Gregg Jaskiewicz <gryzman(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: table spaces
Date: 2013-03-13 16:32:35
Message-ID: CAOR=d=0OusYTxR85aK0dUt3kXtjwzEzYVhxA6WqPL9RZfS7Whw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Mar 13, 2013 at 7:26 AM, Shaun Thomas <sthomas(at)optionshouse(dot)com> wrote:
> On 03/12/2013 05:49 PM, Gregg Jaskiewicz wrote:
>
>> So out of 6 disks then having 4 in Raid 1+0 configuration and other
>> two in mirror for WAL. That's another option then for me to test.
>
>
> That is an option, but it's not necessarily a good one. If all you have are
> six disks, you are probably better off just doing a big RAID-10 for
> everything.

When you've got a smallish number of drives, one big RAID-10 should be
the starting point, and until benchmarks or testing show otherwise
it's usually the best answer.

Note that due to some issues with fsync (esp on ext2/3 partitions) it
is often STILL useful to make a separate partition on that one big
RAID-10 for pg_xlog to live on.

The only real exception to one big RAID-10 on a smallish number of
disks is an almost read only database. In that case using a RAID-5
might be acceptable for the greater amount of storage you can get.
Something like a log analysis or reporting db for instance.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua Berkus 2013-03-13 21:04:58 Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks
Previous Message David Ratcliff 2013-03-13 16:07:09 Breaking news