Skip site navigation (1) Skip section navigation (2)

Re: SAN and full_page_writes

From: "Nikolas Everett" <nik9000(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: SAN and full_page_writes
Date: 2008-09-05 14:24:00
Message-ID: d4e11e980809050724m5f0e8971n3909c26026fda47b@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
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(at)gmail(dot)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(at)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 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++
> +++
>
>

In response to

Responses

pgsql-performance by date

Next:From: Vladimir SitnikovDate: 2008-09-05 15:10:35
Subject: Re: indexing for distinct search in timestamp based table
Previous:From: Claus GuttesenDate: 2008-09-05 12:37:53
Subject: Re: You may need to increase mas_loks_per_trasaction

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group