Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id 08E3F64FCF3
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Wed,  3 Sep 2008 13:03:51 -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 39242-05 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Wed,  3 Sep 2008 13:03:47 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from wa-out-1112.google.com (wa-out-1112.google.com
 [209.85.146.183])
	by postgresql.org (Postfix) with ESMTP id 0319564FCEB
	for <pgsql-performance@postgresql.org>;
	Wed,  3 Sep 2008 13:03:46 -0300 (ADT)
Received: by wa-out-1112.google.com with SMTP id n4so2034889wag.5
	for <pgsql-performance@postgresql.org>;
	Wed, 03 Sep 2008 09:03:46 -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:mime-version:content-type;
	bh=tcJS/rpOG6IA/PyldxBoU+HYqp0CYz06zpmFAbHwzBY=;
	b=fEv7/AsufXoRfb13pblyJJkSbVtH7quDkNXbSVGvM188vFjgSKlNrQvkunYy5oauuR
	HzebD7p+xMLI+1+KVsueQJZKgOGLYTNK/ad5vAsWJoFAvjdcVWVxVM7BG5i8HfQeQuh9
	upyEZUsVgGyFI5HyIOaoIaep0G/I7QMku8s3w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=dPZDXA1Pa539W6gghsM9qHGtiIwpbNU5rXdlZzw6Oj0e5E1x4j3nSwEjXGNytJI4j5
	M1xsrH5ozUMJczAtV5qtXh8sWm8j7r8KG2vbouVHFRw5uLth+waJ7EJN0E5O2y4zcsZe
	rYu7U8ETLVDgEKyTCl7j78RRHiLdqPase7va0=
Received: by 10.114.192.3 with SMTP id p3mr7700189waf.112.1220457825797;
	Wed, 03 Sep 2008 09:03:45 -0700 (PDT)
Received: by 10.114.120.19 with HTTP; Wed, 3 Sep 2008 09:03:45 -0700 (PDT)
Message-ID: <d4e11e980809030903q4e14cf59v291b18e7091e18f6@mail.gmail.com>
Date: Wed, 3 Sep 2008 12:03:45 -0400
From: "Nikolas Everett" <nik9000@gmail.com>
To: pgsql-performance@postgresql.org
Subject: SAN and full_page_writes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_23793_19514786.1220457825787"
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/46
X-Sequence-Number: 31359

------=_Part_23793_19514786.1220457825787
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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_23793_19514786.1220457825787
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">I have the honor to be configuring Postgres to back into a NetApp FAS3020 via fiber.<br><br>Does anyone know if the SAN protects me from breakage due to partial page writes?<br><br>If anyone has an SAN specific postgres knowledge, I&#39;d love to hear your words of wisdom.<br>

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

------=_Part_23793_19514786.1220457825787--