X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AD79E5E46CD for ; Fri, 13 Aug 2004 15:01:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34680-07 for ; Fri, 13 Aug 2004 18:01:39 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id C61195E40BA for ; Fri, 13 Aug 2004 15:01:36 -0300 (ADT) Received: from [64.81.245.111] (HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6069025; Fri, 13 Aug 2004 11:02:52 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: =?iso-8859-15?q?Pierre-Fr=E9d=E9ric=20Caillaud?= , pgsql-performance@postgresql.org Subject: Re: Reiser4 Date: Fri, 13 Aug 2004 11:01:52 -0700 User-Agent: KMail/1.5.4 References: <411CDC24.4090706@archonet.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408131101.52788.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/216 X-Sequence-Number: 7852 Pierre, > Are there any plans in a future Postgresql version to support a special > fsync method for Reiser4 which will use the filesystem's transaction > engine, instead of an old kludge like fsync(), with a possibility of > vastly enhanced performance ? I don't know of any such in progress right now. Why don't you start it? It would have to be an add-in since we support 28 operating systems and Reiser is AFAIK Linux-only, but it sounds like an interesting experiment. > Is there also a possibility to tell Postgres : "I don't care if I lose 30 > seconds of transactions on this table if the power goes out, I just want > to be sure it's still ACID et al. compliant but you can fsync less often > and thus be faster" (with a possibility of setting that on a per-table > basis) ? Not per-table, no, but otherwise take a look at the Background Writer feature of 8.0. -- -Josh Berkus "A developer of Very Little Brain" Aglio Database Solutions San Francisco