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 EE1A332A20F for ; Thu, 30 Sep 2004 17:33:44 +0100 (BST) 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 60722-07 for ; Thu, 30 Sep 2004 16:33:40 +0000 (GMT) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id 4507832A202 for ; Thu, 30 Sep 2004 17:33:38 +0100 (BST) Received: (from markw@localhost) by mail.osdl.org (8.11.6/8.11.6) id i8UGXYg18295; Thu, 30 Sep 2004 09:33:34 -0700 Date: Thu, 30 Sep 2004 09:33:34 -0700 From: Mark Wong To: Guy Thornley Cc: pgsql-performance@postgresql.org Subject: Re: O_DIRECT setting Message-ID: <20040930093334.C11282@osdl.org> References: <20040920075734.GK21733@conker.esphion.com> <20040924080703.A27640@osdl.org> <20040930070232.GA8139@conker.esphion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20040930070232.GA8139@conker.esphion.com>; from guy@esphion.com on Thu, Sep 30, 2004 at 07:02:32PM +1200 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: 200409/343 X-Sequence-Number: 8471 On Thu, Sep 30, 2004 at 07:02:32PM +1200, Guy Thornley wrote: > Sorry about the belated reply, its been busy around here. > > > > Incidentally, postgres heap files suffer really, really bad fragmentation, > > > which affects sequential scan operations (VACUUM, ANALYZE, REINDEX ...) > > > quite drastically. We have in-house patches that somewhat alleiviate this, > > > but they are not release quality. Has anybody else suffered this? > > > > > > > Any chance I could give those patches a try? I'm interested in seeing > > how they may affect our DBT-3 workload, which execute DSS type queries. > > Like I said, the patches are not release quality... if you run them on a > metadata journalling filesystem, without an 'ordered write' mode, its > possible to end up with corrupt heaps after a crash because of garbage data > in the extended files. > > If/when we move to postgres 8 I'll try to ensure the patches get re-done > with releasable quality > > Guy Thornley That's ok, we like to help test and proof things, we don't need patches to be release quality. Mark