X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 95C70D1B474 for ; Thu, 4 Dec 2003 17:58:09 +0000 (GMT) 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 85015-03 for ; Thu, 4 Dec 2003 13:57:39 -0400 (AST) Received: from rlx13.zapatec.com (66-117-144-213.zapatec.lmi.net [66.117.144.213]) by svr1.postgresql.org (Postfix) with ESMTP id 8AFFED1B45B for ; Thu, 4 Dec 2003 13:57:38 -0400 (AST) Received: from rlx11.zapatec.com (rlx11.pr.zapatec.com [192.168.1.132]) by rlx13.zapatec.com (Postfix) with ESMTP id E7059A941 for ; Thu, 4 Dec 2003 09:57:38 -0800 (PST) Received: (from dror@localhost) by rlx11.zapatec.com (8.12.3/8.12.3/Submit) id hB4Hvcjh058970 for pgsql-performance@postgresql.org; Thu, 4 Dec 2003 09:57:38 -0800 (PST) (envelope-from dror) Date: Thu, 4 Dec 2003 09:57:38 -0800 From: Dror Matalon To: pgsql-performance@postgresql.org Subject: Re: tuning questions Message-ID: <20031204175738.GD34796@rlx11.zapatec.com> References: <1070553983.6498.52.camel@cletus.lyris.com> <20031204115932.154eebed.threshar@torgo.978.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031204115932.154eebed.threshar@torgo.978.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/78 X-Sequence-Number: 4938 On Thu, Dec 04, 2003 at 11:59:32AM -0500, Jeff wrote: > On Thu, 04 Dec 2003 08:06:23 -0800 > Jack Coates wrote: > > > testbed: > > dual P3 1.3 GHz box with 2GB RAM > > two IDE 120G drives on separate channels (DMA on), OS on one, DB on > > the other, some swap on each (totalling 2.8G). > > RH Linux 8. > > Side Note: be sure to turn off write caching on those disks or you may > have data corruption in the event of a failure I've seen this comment several times from different people. Would someone care to explain how you would get data corruption? I thought that the whole idea of the log is to provide a journal similar to what you get in a journaling file system. In other words, the db writes a series of transactions to the log and marks that "log entry" (don't know the right nomeclature) as valid. When the db crashes, it reads the log, and discards the last "log entry" if it wasn't marked as valid, and "replays" any transactions that haven't been commited ot the db. The end result being that you might loose your last transaction(s) if the db crashes, but nothing ever gets corrupted. So what am I missing in this picture? Regards, Dror -- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.fastbuzz.com http://www.zapatec.com