From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory Maxwell Subject: Re: reiser4 performance Date: Thu, 11 Aug 2005 17:29:29 -0400 Message-ID: References: <42F7A01A.7090209@namesys.com> <42F7F6DC.2080706@slaphack.com> <42F807D7.9090900@slaphack.com> <42FB9DD7.6080003@namesys.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: Content-Disposition: inline List-Id: Content-Type: text/plain; charset="us-ascii" To: PFC Cc: Hans Reiser , David Masover , ReiserFS List On 8/11/05, PFC wrote: >=20 > > Well, but then you have to tell postgres that it can assume these thing= s > > about reiser4..... >=20 > you can already set the sync mode in the config file to a llot of > different choices, like fdatasync, fsync, O_SYNC, etc, so a reiser4 optio= n > would be possibel I guess. Right, and the PostgreSQL team has already shown that they are willing to create platform specific options. Could someone familiar with the reiser4 internals provide some detailed information about what reiser4 currently provides in this regard? The specific concerns would be about controlling the ordering and atomicity of 8k writes and how to tell when they are fixed to the media.