pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karl Denninger <karl@denninger.net>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Revisiting disk layout on ZFS systems
Date: Mon, 28 Apr 2014 13:29:29 -0500
Message-ID: <535E9E09.1050502@denninger.net> (raw)
In-Reply-To: <CAMkU=1zO6LQ0ESXswPeObOW0c538URd9Mw8LAtcps4qySRtWdQ@mail.gmail.com>
References: <535E781A.5030708@denninger.net>
	<535E9812.1090605@vmware.com>
	<535E98DA.7080702@denninger.net>
	<CAMkU=1zO6LQ0ESXswPeObOW0c538URd9Mw8LAtcps4qySRtWdQ@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>


On 4/28/2014 1:26 PM, Jeff Janes wrote:
> On Mon, Apr 28, 2014 at 11:07 AM, Karl Denninger <karl@denninger.net 
> <mailto:karl@denninger.net>> wrote:
>
>
>
>     Isn't WAL essentially sequential writes during normal operation?
>
>
> Only if you have some sort of non-volatile intermediary, or are 
> willing to risk your data integrity.  Otherwise, the fsync nature 
> trumps the sequential nature.
>
That would be a "no" on the data integrity :-)

-- 
-- Karl
karl@denninger.net

Attachments:

  smime.p7s (application/pkcs7-signature, 2.6K) download

view thread (10+ messages)  latest in thread

Message-ID: <535E9E09.1050502@denninger.net>
Permalink:  ../535E9E09.1050502@denninger.net/
Also on:    postgresql.org/message-id/535E9E09.1050502@denninger.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: karl@denninger.net
  Subject: Re: Revisiting disk layout on ZFS systems
  In-Reply-To: <535E9E09.1050502@denninger.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox