From: Dawid Kuroczko <qnex42@gmail.com>
To: pgsql-performance@postgresql.org
Subject: ext3 journalling type
Date: Mon, 8 Nov 2004 13:26:09 +0100
Message-ID: <758d5e7f04110804263efdf475@mail.gmail.com> (raw)
The ext3fs allows to selet type of journalling to be used with
filesystem. Journalling pretty much "mirrors" the work of WAL
logging by PostgreSQL... I wonder which type of journalling
is best for PgSQL in terms of performance.
Choices include:
journal
All data is committed into the journal prior to being
written into the main file system.
ordered
This is the default mode. All data is forced directly
out to the main file system prior to its metadata being
committed to the journal.
writeback
Data ordering is not preserved - data may be written into
the main file system after its metadata has been commit-
ted to the journal. This is rumoured to be the highest-
throughput option. It guarantees internal file system
integrity, however it can allow old data to appear in
files after a crash and journal recovery.
Am I right to assume that "writeback" is both fastest and at the same
time as safe to use as ordered? Maybe any of you did some benchmarks?
Regards,
Dawid
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: qnex42@gmail.com
Subject: Re: ext3 journalling type
In-Reply-To: <758d5e7f04110804263efdf475@mail.gmail.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