X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 24C325355E for ; Thu, 31 Mar 2005 03:24:41 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37350-10 for ; Thu, 31 Mar 2005 02:24:39 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by svr1.postgresql.org (Postfix) with ESMTP id C4599534CE for ; Thu, 31 Mar 2005 03:24:37 +0100 (BST) Received: from andrei.myip.org ([24.6.189.81]) by comcast.net (rwcrmhc11) with ESMTP id <2005033102244101300do53de>; Thu, 31 Mar 2005 02:24:41 +0000 Received: from localhost (weiqi.home.local [127.0.0.1]) by andrei.myip.org (Postfix) with ESMTP id 3BD97B4067 for ; Wed, 30 Mar 2005 18:24:41 -0800 (PST) Received: from andrei.myip.org ([127.0.0.1]) by localhost (weiqi.home.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00609-02 for ; Wed, 30 Mar 2005 18:24:39 -0800 (PST) Received: from [192.168.2.6] (unknown [192.168.2.6]) by andrei.myip.org (Postfix) with ESMTP id 4AB60B4063 for ; Wed, 30 Mar 2005 18:24:39 -0800 (PST) Subject: Re: fine tuning for logging server From: Florin Andrei Reply-To: pgsql-performance@postgresql.org To: pgsql-performance@postgresql.org In-Reply-To: <424B5982.3090809@arbash-meinel.com> References: <1112233809.10313.31.camel@stantz.corp.sgi.com> <424B5982.3090809@arbash-meinel.com> Content-Type: text/plain Date: Wed, 30 Mar 2005 18:24:38 -0800 Message-Id: <1112235878.12159.22.camel@stantz.corp.sgi.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at andrei.myip.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.031 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/670 X-Sequence-Number: 11375 On Wed, 2005-03-30 at 19:59 -0600, John Arbash Meinel wrote: > Put pg_xlog onto the same drive as the OS, not the drive with the database. I forgot to mention: the OS drive is purposefully made very slow - the write cache is turned off and the FS is Ext3 with data=journal. Is then still ok to put pg_xlog on it? The reason: if the power cord is yanked, the OS _must_ boot back up in good condition. If the DB is corrupted, whatever, nuke it then re- initialize it. But the OS must survive act-of-god events. No, there is no uninterruptible power supply. It sucks, but that's how it is. I cannot change that. -- Florin Andrei http://florin.myip.org/