X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 942FE9DCAB5 for ; Wed, 7 Dec 2005 00:14:54 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 27005-09 for ; Wed, 7 Dec 2005 00:14:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from rwcrmhc12.comcast.net (unknown [216.148.227.153]) by postgresql.org (Postfix) with ESMTP id 5A3B49DCAB1 for ; Wed, 7 Dec 2005 00:14:51 -0400 (AST) Received: from sysexperts.com (c-67-170-228-241.hsd1.ca.comcast.net[67.170.228.241]) by comcast.net (rwcrmhc13) with ESMTP id <20051207041450015004vr81e>; Wed, 7 Dec 2005 04:14:50 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by filer with local; Tue, 06 Dec 2005 20:14:45 -0800 id 0601DBE3.439661B5.00004F8E Date: Tue, 6 Dec 2005 20:14:45 -0800 From: Kevin Brown To: pgsql-performance@postgresql.org Cc: Alex Turner Subject: Re: LVM and Postgres Message-ID: <20051207041445.GA6841@filer> Mail-Followup-To: Kevin Brown , pgsql-performance@postgresql.org, Alex Turner References: <20051206093818.GE6708@campbell-lange.net> <20051206213623.GD14427@campbell-lange.net> <20051207002537.GN7330@mathom.us> <33c6269f0512061652u73a690t8af8a276118b1a83@mail.gmail.com> <20051207013107.GP7330@mathom.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <20051207013107.GP7330@mathom.us> Organization: Frobozzco International User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/217 X-Sequence-Number: 16038 Michael Stone wrote: > Note that the WAL will > wander around the disk as files are created and deleted, whereas tables > are basically updated in place. Huh? I was rather under the impression that the WAL files (in pg_xlog, right?) were reused once they'd been created, so their locations on the disk should remain the same, as should their data blocks (roughly, depending on the implementation of the filesystem, of course). -- Kevin Brown kevin@sysexperts.com