pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Neil Conway <neilc@samurai.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Reece Hart <rkh@gene.COM>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Perfomance Tuning
Date: Tue, 12 Aug 2003 00:37:19 -0400
Message-ID: <20030812043719.GB76772@home.samurai.com> (raw)
In-Reply-To: <200308112259.h7BMxUo14439@candle.pha.pa.us>
References: <1060642567.15483.220.camel@tallac>
	<200308112259.h7BMxUo14439@candle.pha.pa.us>

On Mon, Aug 11, 2003 at 06:59:30PM -0400, Bruce Momjian wrote:
> Uh, the ext2 developers say it isn't 100% reliable --- at least that is
> that was told.  I don't know any personally, but I mentioned it while I
> was visiting Red Hat, and they didn't refute it.

IMHO, if we're going to say "don't use X on production PostgreSQL
systems", we need to have some better evidene than "no one has
said anything to the contrary, and I heard X is bad". If we can't
produce such evidence, we shouldn't say anything at all, and users
can decide what to use for themselves.

(Not that I'm agreeing or disagreeing about ext2 in particular...)

> > My
> > untested interpretation was that the update bookkeeping as well as data
> > update were all getting journalled, the journal space would fill, get
> > sync'd, then repeat. In effect, all blocks were being written TWICE just
> > for the journalling, never mind the overhead for PostgreSQL
> > transactions.

Journalling may or may not have been the culprit, but I doubt everything
was being written to disk twice:

(a) ext3 does metadata-only journalling by default

(b) PostgreSQL only fsyncs WAL records to disk, not the data itself

-Neil




view thread (55+ messages)  latest in thread

Message-ID: <20030812043719.GB76772@home.samurai.com>
Permalink:  ../20030812043719.GB76772@home.samurai.com/
Also on:    postgresql.org/message-id/20030812043719.GB76772@home.samurai.com

 · 

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: neilc@samurai.com, pgman@candle.pha.pa.us, rkh@gene.COM
  Subject: Re: Perfomance Tuning
  In-Reply-To: <20030812043719.GB76772@home.samurai.com>
  References: <1060642567.15483.220.camel@tallac> <200308112259.h7BMxUo14439@candle.pha.pa.us> <20030812043719.GB76772@home.samurai.com>

* 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