pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ragnar <gnari@hive.is>
To: Geoffrey <esoteric@3times25.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: High update activity, PostgreSQL vs BigDBMS
Date: Tue, 02 Jan 2007 14:54:56 +0000
Message-ID: <1167749696.6369.413.camel@localhost.localdomain> (raw)
In-Reply-To: <459A666E.9090508@3times25.net>
References: <45935A49.6080602@burntmail.com>
	<E1H0HFH-0004cw-6E@elasmtp-dupuy.atl.sa.earthlink.net>
	<20061229220747.GB15429@alvh.no-ip.org>
	<459A666E.9090508@3times25.net>

On þri, 2007-01-02 at 09:04 -0500, Geoffrey wrote:
> Alvaro Herrera wrote:
> > 
> > Actually it has been suggested that a combination of ext2 (for WAL) and
> > ext3 (for data, with data journalling disabled) is a good performer.
> > AFAIK you don't want the overhead of journalling for the WAL partition.
> 
> I'm curious as to why ext3 for data with journalling disabled?  Would 
> that not be the same as ext2?

I believe Alvaro was referring to ext3 with journalling enabled 
for meta-data, but not for data.
I also believe this is the standard ext3 configuration, but I
could be wrong on that.

gnari






view thread (39+ messages)  latest in thread

Message-ID: <1167749696.6369.413.camel@localhost.localdomain>
Permalink:  ../1167749696.6369.413.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1167749696.6369.413.camel@localhost.localdomain

 · 

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: gnari@hive.is, esoteric@3times25.net
  Subject: Re: High update activity, PostgreSQL vs BigDBMS
  In-Reply-To: <1167749696.6369.413.camel@localhost.localdomain>

* 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