Re: Optimize update query - Mailing list pgsql-performance

From Vitalii Tymchyshyn
Subject Re: Optimize update query
Date
Msg-id CABWW-d2tzTQ8Wpk-sf6ZgPJpqzU3FAFSQfD523NzS=n7HqV7wg@mail.gmail.com
Whole thread Raw
In response to Re: Optimize update query  (Willem Leenen <willem_leenen@hotmail.com>)
List pgsql-performance
SSDs are not faster for sequential IO as I know. That's why (with BBU or synchronious_commit=off) I prefer to have logs on regular HDDs.

Best reag


2012/11/30 Willem Leenen <willem_leenen@hotmail.com>

 Actually, what's the point in putting logs to ssd? SSDs are good for random access and logs are accessed sequentially. I'd put table spaces on ssd and leave logs on hdd
30 лист. 2012 04:33, "Niels Kristian Schjødt" <nielskristian@autouncle.com> напис.
Because SSD's are considered faster. Then you have to put the most phyisical IO intensive operations on SSD. For the majority of databases, these are the logfiles. But you should investigate where the optimum is for your situation.
 



--
Best regards,
 Vitalii Tymchyshyn

pgsql-performance by date:

Previous
From: Willem Leenen
Date:
Subject: Re: Optimize update query
Next
From: "Kevin Grittner"
Date:
Subject: Re: Optimize update query