From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql@vinz.nl
Cc: pgsql-performance@postgresql.org
Subject: Re: Mount options for Ext3?
Date: Sun, 26 Jan 2003 00:34:48 -0500
Message-ID: <26592.1043559288@sss.pgh.pa.us> (raw)
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>
pgsql.spam@vinz.nl writes:
> 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)
I suppose so ... but if your OS doesn't do *any* re-ordering of writes,
I'd say you need a better OS. Even in Postgres, we'd often like the OS
to collapse multiple writes of the same disk page into one write. And
we certainly want the various writes forced by a sync() to be done with
some intelligence about disk layout, not blindly in order of issuance.
regards, tom lane
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: tgl@sss.pgh.pa.us, pgsql@vinz.nl
Subject: Re: Mount options for Ext3?
In-Reply-To: <26592.1043559288@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> <20030125232154.GK14898@md2.mediadesign.nl> <26592.1043559288@sss.pgh.pa.us>
* 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