Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 21A9B63310E for ; Thu, 25 Mar 2010 17:24:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 70584-01 for ; Thu, 25 Mar 2010 20:24:02 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.216.182]) by mail.postgresql.org (Postfix) with ESMTP id 50C636330DF for ; Thu, 25 Mar 2010 17:24:06 -0300 (ADT) Received: by pxi12 with SMTP id 12so2063197pxi.14 for ; Thu, 25 Mar 2010 13:24:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=P2NEnj6khaULG0pCUyFX+giKviGHmzD9J14tMUJel4s=; b=O32BmpgDIiX7tHfwQGHqYRIKNWGJ58OlphGxmdZA1SeUOc4CwS/TM2rMGMsITjgp6W /1hleYy9Pet+VJ/8vjWl610b+VYblbTbVUavWVxfvEJnPOFNDEpqat+BBCKLNbgQnDii urs+XXoa5MOZ8xvDBauCbmqa5DtZUu8bX6oPc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wivwzU38IPsVKlFY5sV2iDpFFgWb7vRzPFSkwuDhwhzYE3TbQZj/KWC015PI2yQrUa 5rtOUJTfR5H5dDAS+AH1NyN1y+H1AQEDA1tIIE4maV9Vhk11v2UUNHpyLd98rtbXXEin LLn5YMe+nDKgHvDkKEzOt285RoDk3++xLJYOs= MIME-Version: 1.0 Received: by 10.114.54.34 with SMTP id c34mr1069742waa.33.1269548644727; Thu, 25 Mar 2010 13:24:04 -0700 (PDT) In-Reply-To: <4BABC1E0.7010607@mansionfamily.plus.com> References: <4BA23936.2030507@gmail.com> <4BA596D2.4050406@squeakycode.net> <20100323185232.GD6662@rice.edu> <5342.1269372121@sss.pgh.pa.us> <4BA934B9.9070401@2ndquadrant.com> <4BA9D39B.6020103@gmail.com> <1269421198.11473.50.camel@hvost> <4BABC1E0.7010607@mansionfamily.plus.com> Date: Thu, 25 Mar 2010 14:24:04 -0600 Message-ID: Subject: Re: mysql to postgresql, performance questions From: Scott Marlowe To: James Mansion Cc: Hannu Krosing , Yeb Havinga , Greg Smith , Tom Lane , "Ross J. Reedstrom" , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.767 tagged_above=-10 required=5 tests=AWL=-1.582, BAYES_40=-0.185, SARE_OEM_OBFU=1 X-Spam-Level: X-Archive-Number: 201003/325 X-Sequence-Number: 38150 On Thu, Mar 25, 2010 at 2:04 PM, James Mansion wrote: > Hannu Krosing wrote: >> >> Pulling the plug should not corrupt a postgreSQL database, unless it was >> using disks which lie about write caching. >> > > Didn't we recently put the old wife's 'the disks lied' tale to bed in favour > of actually admiting that some well known filesystems and saftware raid > systems have had trouble with their write barriers? I believe so. It was determined to be a combination of several culprits, and only a few hard drives from back in the day apparently ever had this problem. Of course now it seems that modern SSDs may lie about cache if they don't have a big enough capacitor to guarantee they can write out their internal cache etc. The sad fact remains that many desktop / workstation systems lie, and quite a few servers as well, for whatever reason.