Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 660849FA572 for ; Thu, 1 Nov 2007 04:52:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 92446-05 for ; Thu, 1 Nov 2007 04:52:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 1C6389FA56A for ; Thu, 1 Nov 2007 04:52:13 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id BCAB5DCC9E8; Thu, 1 Nov 2007 08:52:12 +0100 (CET) Message-ID: <472985B5.6010701@hagander.net> Date: Thu, 01 Nov 2007 08:52:21 +0100 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Ow Mun Heng CC: Tomas Vondra , Ketema , pgsql-performance@postgresql.org Subject: Re: Hardware for PostgreSQL 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> In-Reply-To: <1193903161.9148.27.camel@neuromancer.home.net> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/7 X-Sequence-Number: 27422 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