Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0D1D69FB2BA for ; Mon, 26 Feb 2007 17:51:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 35273-04 for ; Mon, 26 Feb 2007 17:51:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from servata.com (ip-216-152-249-241.servata.com [216.152.249.241]) by postgresql.org (Postfix) with ESMTP id 7E31F9FB270 for ; Mon, 26 Feb 2007 17:51:17 -0400 (AST) Received: from [209.162.219.253] (helo=dogma.v10.wvs) by servata.com with esmtpa (Exim 4.50) id 1HLnkO-0008CP-Rj; Mon, 26 Feb 2007 13:51:05 -0800 Subject: Re: Two hard drives --- what to do with them? From: Jeff Davis To: Peter Kovacs Cc: Tom Lane , Carlos Moreno , pgsql-performance@postgresql.org In-Reply-To: References: <45DF3B15.1070609@3times25.net> <200702231330.57014.josh@agliodbs.com> <45DF5DA9.90002@commandprompt.com> <45DF6154.5090205@3times25.net> <1d4e0c10702231425ke37a732y36e241902fe0aa55@mail.gmail.com> <45DF94BF.6050904@3times25.net> <45E0A500.1010707@commandprompt.com> <45E104DD.3080600@mochima.com> <2055.1172375931@sss.pgh.pa.us> Content-Type: text/plain Date: Mon, 26 Feb 2007 13:51:06 -0800 Message-Id: <1172526666.10824.315.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.18 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200702/313 X-Sequence-Number: 23367 On Sun, 2007-02-25 at 23:11 +0100, Peter Kovacs wrote: > A related question: > Is it sufficient to disable write cache only on the disk where pg_xlog > is located? Or should write cache be disabled on both disks? > When PostgreSQL does a checkpoint, it thinks the data pages before the checkpoint have successfully made it to disk. If the write cache holds those data pages, and then loses them, there's no way for PostgreSQL to recover. So use a battery backed cache or turn off the write cache. Regards, Jeff Davis