Skip site navigation (1) Skip section navigation (2)

Re: What exactly is postgres doing during INSERT/UPDATE ?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jeff Janes" <jeff(dot)janes(at)gmail(dot)com>, "Joseph S" <jks(at)selectacast(dot)net>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?
Date: 2009-08-31 16:31:13
Message-ID: 4A9BB481020000250002A62F@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Joseph S <jks(at)selectacast(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Scott MarloweDate: 2009-08-31 19:15:56
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?
Previous:From: Jeff JanesDate: 2009-08-31 15:24:01
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group