Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 8A0FC1337B69 for ; Fri, 29 Oct 2010 15:49:29 -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 21937-08 for ; Fri, 29 Oct 2010 18:49:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 380D01337B63 for ; Fri, 29 Oct 2010 15:49:21 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 4AD7D348017; Fri, 29 Oct 2010 11:49:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jce3RCMCpbgy; Fri, 29 Oct 2010 11:49:18 -0700 (PDT) Received: from perhan.alvh.no-ip.org (unknown [200.85.213.6]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id CCF52348015; Fri, 29 Oct 2010 11:49:17 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 7A8066E8C0; Fri, 29 Oct 2010 15:49:12 -0300 (CLST) Content-Type: text/plain; charset=UTF-8 Cc: Bruce Momjian , Scott Marlowe , jd , Ben Chobot , Steve Crawford , pgsql-performance Subject: Re: BBU Cache vs. spindles From: Alvaro Herrera To: Greg Smith In-reply-to: <4CC07291.8020601@2ndquadrant.com> References: <201010211651.o9LGp9I28474@momjian.us> <4CC07291.8020601@2ndquadrant.com> Date: Fri, 29 Oct 2010 15:49:12 -0300 Message-Id: <1288377894-sup-2286@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.324 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_NJABL_PROXY=2.224 X-Spam-Level: X-Archive-Number: 201010/586 X-Sequence-Number: 41004 Excerpts from Greg Smith's message of jue oct 21 14:04:17 -0300 2010: > What I would like to do is beef up the documentation with some concrete > examples of how to figure out if your cache and associated write path > are working reliably or not. It should be possible to include "does > this handle full page writes correctly?" in that test suite. Until we > have something like that, I'm concerned that bugs in filesystem or > controller handling may make full_page_writes unsafe even with a BBU, > and we'd have no way for people to tell if that's true or not. I think if you assume that there are bugs in the filesystem which you need to protect against, you are already hosed. I imagine there must be some filesystem bug that makes it safe to have full_page_writes=on, but unsafe to have full_page_writes=off; but I'd probably discard those as a rare minority and thus not worth worrying about. I agree it would be worth testing though. -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support