pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Mount options for Ext3?
Date: 26 Jan 2003 02:04:45 -0600
Message-ID: <1043568285.818.241.camel@haggis> (raw)
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>

On Sat, 2003-01-25 at 23:34, Tom Lane wrote:
> 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.

And anyway, wouldn't SCSI's Tagged Command Queueing override it all,
no matter if the OS did re-ordering or not?

But then, it really means it when it says that fsync() succeeds, so does
TCQ matter in this case?

-- 
+---------------------------------------------------------------+
| Ron Johnson, Jr.        mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA      http://members.cox.net/ron.l.johnson  |
|                                                               |
| "Fear the Penguin!!"                                          |
+---------------------------------------------------------------+




view thread (14+ messages)  latest in thread

Message-ID: <1043568285.818.241.camel@haggis>
Permalink:  ../1043568285.818.241.camel@haggis/
Also on:    postgresql.org/message-id/1043568285.818.241.camel@haggis

 · 

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: ron.l.johnson@cox.net
  Subject: Re: Mount options for Ext3?
  In-Reply-To: <1043568285.818.241.camel@haggis>
  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> <1043568285.818.241.camel@haggis>

* 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