Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7900764FCD7 for ; Fri, 5 Sep 2008 11:24:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 16701-09 for ; Fri, 5 Sep 2008 11:24:02 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by postgresql.org (Postfix) with ESMTP id 70E4264FCBA for ; Fri, 5 Sep 2008 11:24:02 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so260449yxb.73 for ; Fri, 05 Sep 2008 07:24:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=FYySqqRwL8H2meFAdb/evMs7Wqan2Ck8SmIRhDhwyLs=; b=KhplPqsh+m0jJedsucYFZRGDkh/A7+rfgQur6A90Lyum906gObkrHuhr6VfXDiBZ20 Yuw1rs4KEQiEic0/8OICSOr6hCBBYpES/57l3S/aVGAMu7+OrsRtB/WnWF+7Zn/my0XL crsMgWYeoG9k7K0tp9uhptVBDpnzOH++pvoZw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=wMJdAUjL59zEfpJ5clJA/IoX7Il3JcN7WUqTqDyxG+vFQVlKZ1sMOk4rs/2YA2sWnp 8a4fWXt/Q7k63BypMHnYdGYRx1j3Fd8YlPZuTVyJY5cyiZjuvxqgpRAccaiSVPD6cUL2 Fayi+geYRt0KjiweEkXI8v/78obpFyVAPTOJY= Received: by 10.115.90.1 with SMTP id s1mr10029987wal.214.1220624640181; Fri, 05 Sep 2008 07:24:00 -0700 (PDT) Received: by 10.114.120.19 with HTTP; Fri, 5 Sep 2008 07:24:00 -0700 (PDT) Message-ID: Date: Fri, 5 Sep 2008 10:24:00 -0400 From: "Nikolas Everett" To: pgsql-performance@postgresql.org Subject: Re: SAN and full_page_writes In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25857_24444840.1220624640192" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200809/73 X-Sequence-Number: 31386 ------=_Part_25857_24444840.1220624640192 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I seem to have answered my own question. I'm sending the answer to the list in case someone else has the same question one day. According to the NetApp documentation, it does protect me from partial page writes. Thus, full_page_writes = off. On Wed, Sep 3, 2008 at 12:03 PM, Nikolas Everett wrote: > I have the honor to be configuring Postgres to back into a NetApp FAS3020 > via fiber. > > Does anyone know if the SAN protects me from breakage due to partial page > writes? > > If anyone has an SAN specific postgres knowledge, I'd love to hear your > words of wisdom. > > For reference: > [postgres@localhost bonnie]$ ~neverett/bonnie++-1.03a/bonnie++ > Writing with putc()...done > Writing intelligently...done > Rewriting...done > Reading with getc()...done > Reading intelligently...done > start 'em...done...done...done... > Create files in sequential order...done. > Stat files in sequential order...done. > Delete files in sequential order...done. > Create files in random order...done. > Stat files in random order...done. > Delete files in random order...done. > Version 1.03 ------Sequential Output------ --Sequential Input- > --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- > --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec > %CP > localhost.lo 32104M 81299 94 149848 30 42747 8 45465 61 55528 4 > 495.5 0 > ------Sequential Create------ --------Random > Create-------- > -Create-- --Read--- -Delete-- -Create-- --Read--- > -Delete-- > files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec > %CP > 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ > +++ > > ------=_Part_25857_24444840.1220624640192 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
I seem to have answered my own question.  I'm sending the answer to the list in case someone else has the same question one day.

According to the NetApp documentation, it does protect me from partial page writes.  Thus, full_page_writes = off.


On Wed, Sep 3, 2008 at 12:03 PM, Nikolas Everett <nik9000@gmail.com> wrote:
I have the honor to be configuring Postgres to back into a NetApp FAS3020 via fiber.

Does anyone know if the SAN protects me from breakage due to partial page writes?

If anyone has an SAN specific postgres knowledge, I'd love to hear your words of wisdom.

For reference:
[postgres@localhost bonnie]$ ~neverett/bonnie++-1.03a/bonnie++
Writing with putc()...done
Writing intelligently...done
Rewriting...done
Reading with getc()...done
Reading intelligently...done
start 'em...done...done...done...
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...done.
Create files in random order...done.
Stat files in random order...done.
Delete files in random order...done.
Version  1.03       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
localhost.lo 32104M 81299  94 149848  30 42747   8 45465  61 55528   4 495.5   0
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++


------=_Part_25857_24444840.1220624640192--