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 A87DBD1B43F for ; Thu, 4 Dec 2003 18:12:23 +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 87707-03 for ; Thu, 4 Dec 2003 14:11:53 -0400 (AST) Received: from mail.libertyrms.com (unknown [209.167.124.227]) by svr1.postgresql.org (Postfix) with ESMTP id 4630CD1B468 for ; Thu, 4 Dec 2003 14:11:52 -0400 (AST) Received: from [10.1.2.146] (helo=dba3.int.libertyrms.info) by mail.libertyrms.com with esmtp (Exim 3.22 #3 (Debian)) id 1ARxxA-0003CA-00 for ; Thu, 04 Dec 2003 13:11:52 -0500 Received: by dba3.int.libertyrms.info (Postfix, from userid 1019) id 6889A138F4; Thu, 4 Dec 2003 13:11:52 -0500 (EST) Date: Thu, 4 Dec 2003 13:11:52 -0500 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: tuning questions Message-ID: <20031204181152.GO6080@libertyrms.info> Mail-Followup-To: Andrew Sullivan , pgsql-performance@postgresql.org References: <1070553983.6498.52.camel@cletus.lyris.com> <20031204115932.154eebed.threshar@torgo.978.org> <20031204175738.GD34796@rlx11.zapatec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031204175738.GD34796@rlx11.zapatec.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/80 X-Sequence-Number: 4940 On Thu, Dec 04, 2003 at 09:57:38AM -0800, Dror Matalon wrote: > > 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. > So what am I missing in this picture? That a journalling file system can _also_ have file corruption if you have write caching enabled and no battery back up. If the drive tells the OS, "Yep! It's all on the disk!" bit it is _not_ actually scribed in the little bitty magnetic patterns -- and at that very moment, the power goes away -- the data that was reported to have been on the disk, but which was actually _not_ on the disk, is no longer anywhere. (Well, except in the past. But time travel was disabled some versions ago. ;-) A -- ---- Andrew Sullivan 204-4141 Yonge Street Afilias Canada Toronto, Ontario Canada M2P 2A8 +1 416 646 3304 x110