From: Magnus Hagander <magnus@hagander.net>
To: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
Cc: Tomas Vondra <tv@fuzzy.cz>
Cc: Ketema <ketema@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware for PostgreSQL
Date: Thu, 01 Nov 2007 08:52:21 +0100
Message-ID: <472985B5.6010701@hagander.net> (raw)
In-Reply-To: <1193903161.9148.27.camel@neuromancer.home.net>
References: <1193849108.591961.103570@22g2000hsm.googlegroups.com>
<4728FAA1.7060905@fuzzy.cz>
<1193889182.7999.71.camel@neuromancer.home.net>
<4729783A.2030201@hagander.net>
<1193903161.9148.27.camel@neuromancer.home.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: magnus@hagander.net, Ow.Mun.Heng@wdc.com, tv@fuzzy.cz, ketema@gmail.com
Subject: Re: Hardware for PostgreSQL
In-Reply-To: <472985B5.6010701@hagander.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox