Re: WAL documentation changes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WAL documentation changes
Date: 2008-12-16 03:44:50
Message-ID: 200812160344.mBG3iov14875@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
>
> >> First, none of the general purpose filesystems I've seen so far do data
> >> journalling per default, since it's a huge performance penalty, even for
> >> non-RDBMS workloads. The feature you talk about is ext3 specific (and
> >> should be pointed out as such) and only disables write ordering, meaning
> >> that metadata and file content updates are not synchronized.
> >
> > You are right that my docs were misleading. I have improved them by
> > mentioning that it is _data_ flush that as part of journalling that can
> > be a problem, and documented that the mount option listed is
> > ext3-specific, not linux-specific.
>
> Actually, I think that some of the other journalling filesystems allow
> data journalling (I know ReiserFS does), they just don't default to it.
> For that matter, a few (ZFS in particular) have data journalling which
> can't be turned off. While it's not a tuning parameter, users should be
> warned that they'll take a performance hit from it.

So I assume you are saying the docs are fine now.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2008-12-16 03:55:38 Re: 8.4 replication questions
Previous Message Fujii Masao 2008-12-16 03:44:47 Re: Multiplexing SUGUSR1