Re: Optimize update query

From: Willem Leenen <willem_leenen(at)hotmail(dot)com>
To: <tivv00(at)gmail(dot)com>, <nielskristian(at)autouncle(dot)com>
Cc: <kgrittn(at)mail(dot)com>, <sthomas(at)optionshouse(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Optimize update query
Date: 2012-11-30 10:14:15
Message-ID: DUB104-W4140CECF592B7AC5F411768F430@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)autouncle(dot)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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Vitalii Tymchyshyn 2012-11-30 10:31:52 Re: Optimize update query
Previous Message Vitalii Tymchyshyn 2012-11-30 10:07:53 Re: Optimize update query