Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1A39C475B33 for ; Fri, 24 Jan 2003 20:16:46 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 514A9475461 for ; Fri, 24 Jan 2003 20:16:45 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0P1Gm5u028177; Fri, 24 Jan 2003 20:16:48 -0500 (EST) To: Kevin Brown Cc: pgsql-performance@postgresql.org Subject: Re: Mount options for Ext3? In-reply-to: <20030125003011.GA28252@filer> References: <200301241120.14404.josh@agliodbs.com> <20030125003011.GA28252@filer> Comments: In-reply-to Kevin Brown message dated "Fri, 24 Jan 2003 16:30:11 -0800" Date: Fri, 24 Jan 2003 20:16:48 -0500 Message-ID: <28176.1043457408@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/313 X-Sequence-Number: 960 Kevin Brown writes: > I suspect the answer to that is that you can safely turn off fsync > only if the operating system will guarantee that write transactions > from a process are actually committed in the order they arrive from > that process. Yeah. We use fsync partly so that when we tell a client a transaction is committed, it really is committed (ie, down to disk) --- but also as a means of controlling write order. I strongly doubt that any modern filesystem will promise to execute writes exactly in the order issued, unless prodded by means such as fsync. > Otherwise you'd have to worry about write transactions > to the transaction log committing before the writes to the data files > during a savepoint, Actually, the other way around is the problem. The WAL algorithm works so long as log writes hit disk before the data-file changes they describe (that's why it's called write *ahead* log). regards, tom lane