From: Chris <list@1006.org>
To: pgsql-performance@postgresql.org
Subject: Re: data=writeback
Date: Thu, 08 Apr 2004 11:01:29 +0200
Message-ID: <1081414889.5037.29.camel@dell> (raw)
In-Reply-To: <2A07EC2D0BC2774AAD6F74769F60D52A0832C6@ahmose.cict_ad.nl>
References: <2A07EC2D0BC2774AAD6F74769F60D52A0832C6@ahmose.cict_ad.nl>
> LABEL=/usr/local/pgsql /usr/local/pgsql ext3
> noatime,data=writeback 1 2
> LABEL=/usr/local/pgsql /usr/local/pgsql/wal ext3
> noatime,data=ordered 1 2
The same label mounted on two different mount points is probably I typo?
I'm not sure if data=writeback is ok. I was wondering about the same
thing after reading the "good pc but bad performance,why?" thread.
This is from man mount:
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.
How does this relate to fflush()? Does fflush still garantee
all data has ben written?
Bye, Chris.
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: list@1006.org
Subject: Re: data=writeback
In-Reply-To: <1081414889.5037.29.camel@dell>
* 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