Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E4FD36323AA for ; Sat, 5 Jun 2010 19:37:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 65906-01 for ; Sat, 5 Jun 2010 22:36:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 8E7E963234F for ; Sat, 5 Jun 2010 19:36:55 -0300 (ADT) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LrIS4-1PJMsg3lPw-013B8b; Sun, 06 Jun 2010 00:36:51 +0200 Message-ID: <4C0AD180.90607@2ndquadrant.com> Date: Sat, 05 Jun 2010 18:36:48 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Jon Schewe CC: pgsql-performance@postgresql.org Subject: Re: How filesystems matter with PostgreSQL References: <4C08EEDF.7090403@mtu.net> In-Reply-To: <4C08EEDF.7090403@mtu.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+2uDGt74+jmE/TFKUD1zVGG6uQHFepOLwoIrj 3ud/8yyzLfG86dek1dfFGFMyBWrJFSIedZRGZmu1Uod3k6bE89 qrn8MZ+yzF+PWPpi1rQ6JGuAgKMALmY X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.8 tagged_above=-10 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201006/114 X-Sequence-Number: 38970 Jon Schewe wrote: > The tests were all done on an opensuse 11.2 64-bit machine, > on the same hard drive (just ran mkfs between each test) on the same > input with the same code base. So no controller card, just the motherboard and a single hard drive? If that's the case, what you've measured is which filesystems are safe because they default to flushing drive cache (the ones that take around 15 minutes) and which do not (the ones that take >=around 2 hours). You can't make ext3 flush the cache correctly no matter what you do with barriers, they just don't work on ext3 the way PostgreSQL needs them to. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us