X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2F99ED1B366 for ; Sat, 29 May 2004 15:31:33 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 60225-01 for ; Sat, 29 May 2004 15:31:32 -0300 (ADT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id A1C0ED1CECA for ; Sat, 29 May 2004 15:31:11 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by www.postgresql.com (Postfix) with ESMTP id 62FE3CF6A7A for ; Sat, 29 May 2004 12:19:51 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i4TFI6SZ020196; Sat, 29 May 2004 11:18:07 -0400 (EDT) To: shridhar@frodo.hserus.net Cc: share-postgres@think42.com, Richard Huxton , pgsql-performance@postgresql.org Subject: Re: filesystem option tuning In-reply-to: <200405291501.45229.shridhar@frodo.hserus.net> References: <20040515125227.A29574@p15097255.pureserver.info> <40A8F0B6.6060703@archonet.com> <20040519093239.A26016@p15097255.pureserver.info> <200405291501.45229.shridhar@frodo.hserus.net> Comments: In-reply-to Shridhar Daithankar message dated "Sat, 29 May 2004 15:01:45 +0530" Date: Sat, 29 May 2004 11:18:06 -0400 Message-ID: <20195.1085843886@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/227 X-Sequence-Number: 7058 Shridhar Daithankar writes: > On Wednesday 19 May 2004 13:02, share-postgres@think42.com wrote: > - If you can put WAL on separate disk(s), all the better. >> >> Does that mean only the xlog, or also the clog? > You can put clog and xlog on same drive. You can, but I think you shouldn't. The entire argument for giving xlog its own drive revolves around the fact that xlog is written sequentially, and so if it has its own spindle then you have near-zero seek requirements. As soon as you give that drive any other work to do, you start losing the low-seek property. Now as Shridhar says, clog is not a very high-I/O-volume thing, so in one sense it doesn't much matter which drive you put it on. But it seems to me that clog acts much more like ordinary table files than it acts like xlog. regards, tom lane