Received: from maia.hub.org (unknown [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3D4361337990 for ; Sun, 24 Oct 2010 14:05:09 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 51354-01 for ; Sun, 24 Oct 2010 17:05:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.postgresql.org (Postfix) with ESMTP id EF5C71336473 for ; Sun, 24 Oct 2010 14:05:00 -0300 (ADT) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MHKOl-1PO4Dt2vch-00DVNR; Sun, 24 Oct 2010 19:04:48 +0200 Message-ID: <4CC4672D.9040401@2ndquadrant.com> Date: Sun, 24 Oct 2010 13:04:45 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Jesper Krogh CC: Tom Lane , Kevin Grittner , Bruce Momjian , jd@commandprompt.com, Scott Marlowe , Steve Crawford , pgsql-performance@postgresql.org, Ben Chobot Subject: Re: BBU Cache vs. spindles References: <4CC04EA50200002500036C5E@gw.wicourts.gov> <201010211935.o9LJZTM21744@momjian.us> <4CC0513E0200002500036C68@gw.wicourts.gov> <4CC1094C.1090306@2ndquadrant.com> <13038.1287720327@sss.pgh.pa.us> <4CC1AFB3.3000903@2ndquadrant.com> <4CC1BD86.8070006@krogh.cc> In-Reply-To: <4CC1BD86.8070006@krogh.cc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:IPoEW2/IeNOUx70Fw1v6vKXUcIUnZF9KeVlxvmlZ6kT uQapXu8adb1LXhSM5E8JKRiIp3uomYzdb8yLoWAJDrE2/IB4k1 uRoI0lZaFLF+GFp6HXsjXxDRRljvJg8+Y4B+tfW1bDw85yTtYS X4/TSA8O1pA/Dsifi/onYKjaGYkZc3BquBmdQuKaIWHuACef+w N0ub3QShSJJPDIzyUs9jNqyJ8sGBcrnMo0wts129u8= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/393 X-Sequence-Number: 40811 Jesper Krogh wrote: > Can you point to some ZFS docs that tell that this is the case.. I'd > be surprised > if it doesnt copy away the old block and replaces it with the new one > in-place. The > other behaviour would quite quickly lead to a hugely fragmented > filesystem that > performs next to useless and ZFS doesnt seem to be in that category.. http://all-unix.blogspot.com/2007/03/zfs-cow-and-relate-features.html "Blocks containing active data are never overwritten in place; instead, a new block is allocated, modified data is written to it, and then any metadata blocks referencing it are similarly read, reallocated, and written." http://opensolaris.org/jive/thread.jspa?messageID=19264 discusses how this interacts with the common types of hardware around: no guaratees with lying hard drives as always, but otherwise you're fine. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books