Ow Mun Heng wrote:
>> You're likely better off (performance-wise) putting it on the same disk
>> as the database itself if that one has better RAID, for example.
>
> I'm thinking along the lines of since nothing much writes to the OS
> Disk, I should(keyword) be safe.
Unless it's *always* in the cache (not so likely), reads will also move
the heads...
In the situation you have, I'd put the xlog on the same disk as the data
- mainly because it gives you RAID on it in case the disk breaks.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
