X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D3A52D1D29F; Thu, 25 Mar 2004 19:11:26 +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 25335-09; Thu, 25 Mar 2004 15:11:30 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 7B2D5D1B88F; Thu, 25 Mar 2004 15:11:24 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4693080; Thu, 25 Mar 2004 11:12:47 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Bruce Momjian , markw@osdl.org Subject: Re: [HACKERS] fsync method checking Date: Thu, 25 Mar 2004 11:10:55 -0800 User-Agent: KMail/1.5.4 Cc: manfred@colorfullife.com, tgl@sss.pgh.pa.us, Q@ping.be, markir@paradise.net.nz, pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org References: <200403251852.i2PIquv29582@candle.pha.pa.us> In-Reply-To: <200403251852.i2PIquv29582@candle.pha.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403251110.55889.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/362 X-Sequence-Number: 6218 Bruce, > We don't actually extend the WAL file during writes (preallocated), and > the access/modification timestamp is only in seconds, so I wonder of the > OS only updates the inode once a second. What else would change in the > inode more frequently than once a second? What about really big writes, when WAL files are getting added/recycled? -- -Josh Berkus Aglio Database Solutions San Francisco