Postgres Pro
Downloads
Home   >   mailing lists

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

From Jeff Janes
Subject Re: What exactly is postgres doing during INSERT/UPDATE ?
Date
Msg-id f67928030908310824n1f06cc7wf47a4755513d1a9f@mail.gmail.com
Whole thread Raw
In response to Re: What exactly is postgres doing during INSERT/UPDATE ?  (Joseph S <jks@selectacast.net>)
Responses Re: What exactly is postgres doing during INSERT/UPDATE ?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-performance
Tree view
On Sun, Aug 30, 2009 at 1:01 PM, Joseph S <jks@selectacast.net> wrote:
I've already learned my lesson and will never use raid 5 again.  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?  I haven't encountered this debate in in the pgsql world, but from the Oracle world it seems to me the "Stripe And Mirror Everything" people had the better argument than the "separate tables and indexes" people.


Jeff

pgsql-performance by date:

Previous
From: Aidan Van Dyk
Date:
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?
Next
From: "Kevin Grittner"
Date:
Subject: Re: What exactly is postgres doing during INSERT/UPDATE ?