Re: What exactly is postgres doing during INSERT/UPDATE ? - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: What exactly is postgres doing during INSERT/UPDATE ?
Date
Msg-id 4A9BB481020000250002A62F@gw.wicourts.gov
Whole thread Raw
In response to Re: What exactly is postgres doing during INSERT/UPDATE ?  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: What exactly is postgres doing during INSERT/UPDATE ?
List pgsql-performance
Jeff Janes <jeff.janes@gmail.com> wrote:
> Joseph S <jks@selectacast.net> wrote:

>> The question is what I do with my 14 drives. Should I use only 1
>> pair for indexes or should I use 4 drives?  The wal logs are
>> already slated for an SSD.

> Why not just spread all your index data over 14 spindles, and do the
> same with your table data?

If you have the luxury of being able to test more than one
configuration with something resembling your actual workload, I would
strongly recommend including this as one of your configurations.
Spreading everything over the larger number of spindles might well
out-perform your most carefully hand-crafted tuning of object
placement on smaller spindle sets.

-Kevin

pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?
Next
From: Scott Marlowe
Date:
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?