pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: pgsql.spam@vinz.nl
To: pgsql-performance@postgresql.org
Subject: Re: Mount options for Ext3?
Date: Sun, 26 Jan 2003 00:21:54 +0100
Message-ID: <20030125232154.GK14898@md2.mediadesign.nl> (raw)
In-Reply-To: <1260.1043463535@sss.pgh.pa.us>
References: <200301241120.14404.josh@agliodbs.com>
	<20030125003011.GA28252@filer>
	<28176.1043457408@sss.pgh.pa.us>
	<20030125021159.GC28252@filer>
	<1260.1043463535@sss.pgh.pa.us>

On 2003-01-24 21:58:55 -0500, Tom Lane wrote:
> The key assumption we are making about the filesystem's behavior is that
> writes scheduled by the sync() will occur before the pg_control write
> that's issued after it.  People have occasionally faulted this algorithm
> by quoting the sync() man page, which saith (in the Gospel According To
> HP)
> 
>      The writing, although scheduled, is not necessarily complete upon
>      return from sync.
> 
> This, however, is not a problem in itself.  What we need to know is
> whether the filesystem will allow writes issued after the sync() to
> complete before those "scheduled" by the sync().
> 

Certain linux 2.4.* kernels (not sure which, newer ones don't seem to have 
it) have the following kernel config option:

Use the NOOP Elevator (WARNING)
CONFIG_BLK_DEV_ELEVATOR_NOOP
  If you are using a raid class top-level driver above the ATA/IDE core,
  one may find a performance boost by preventing a merging and re-sorting
  of the new requests.

  If unsure, say N.

If one were certain his OS wouldn't do any re-ordering of writes, would it be
safe to run with fsync = off? (not that I'm going to try this, but I'm just
curious)


Vincent van Leeuwen
Media Design



view thread (14+ messages)  latest in thread

Message-ID: <20030125232154.GK14898@md2.mediadesign.nl>
Permalink:  ../20030125232154.GK14898@md2.mediadesign.nl/
Also on:    postgresql.org/message-id/20030125232154.GK14898@md2.mediadesign.nl

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: pgsql.spam@vinz.nl
  Subject: Re: Mount options for Ext3?
  In-Reply-To: <20030125232154.GK14898@md2.mediadesign.nl>
  References: <200301241120.14404.josh@agliodbs.com> <20030125003011.GA28252@filer> <28176.1043457408@sss.pgh.pa.us> <20030125021159.GC28252@filer> <1260.1043463535@sss.pgh.pa.us> <20030125232154.GK14898@md2.mediadesign.nl>

* 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