Received: from maia.hub.org (unknown [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id D9A4C1337B54 for ; Thu, 21 Oct 2010 11:08:18 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 09924-02 for ; Thu, 21 Oct 2010 14:08:08 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 428121337B96 for ; Thu, 21 Oct 2010 11:08:08 -0300 (ADT) Received: from [192.168.1.7] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LaYSx-1OmpLd3mnf-00lwgo; Thu, 21 Oct 2010 16:08:07 +0200 Message-ID: <4CC04945.7030100@2ndquadrant.com> Date: Thu, 21 Oct 2010 10:08:05 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: pgsql-performance Subject: New wiki page on write reliability Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:mHCkJYwScpAD+23r25RqzsnokrreL/YJ8sLUtleYR4Y Z6tdd2OQhNxnmK/ZDzjN9Dt6K0QhBfss51QaLbaZ4CMriX/xGJ syeFAmwIPAUf8nDbz9zPctnjqI1CsnZOy+PwA45EuviPJgJ+cM ZWnRg8QAnIaoSNK0XXOOBD5e3ChO9fN5kY189KdTt+VhVR2Kc2 RbxLW4QZwm3WDs1FFZW1SXGbP0EXN7iJE0Z3YXiVP8= 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/342 X-Sequence-Number: 40760 Now that some of my recent writing has gone from NDA protected to public sample, I've added a new page to the PostgreSQL wiki that provides a good starting set of resources to learn about an ever popular topic here, how write cache problems can lead to database corruption: http://wiki.postgresql.org/wiki/Reliable_Writes Bruce also has a presentation he's been working on that adds pictures showing the flow of data through the various cache levels, to help people visualize the whole thing, that should get added into there once he's finished tweaking it. I'd like to get some feedback from the members of this list about what's still missing after this expanded data dump. Ultimately I'd like to get this page to be an authoritative enough resource that the "Reliability" section of the official documentation could point back to this as a recommendation for additional information. So much of this material requires singling out specific vendors and staying up to date with hardware changes, both things that the official docs are not a good place for. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance": http://www.2ndquadrant.com/books