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 27B9C329CB0 for ; Thu, 30 Sep 2004 08:02:49 +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 55725-04 for ; Thu, 30 Sep 2004 07:02:38 +0000 (GMT) Received: from mail.esphion.com (mail.esphion.com [202.6.75.178]) by svr1.postgresql.org (Postfix) with ESMTP id 2B8BE32A0A1 for ; Thu, 30 Sep 2004 08:02:35 +0100 (BST) Received: (qmail 22644 invoked from network); 30 Sep 2004 07:01:57 -0000 Received: from unknown (HELO conker.?none?) (10.0.1.137) by mail.esphion.com with SMTP; 30 Sep 2004 07:01:57 -0000 Received: (nullmailer pid 21525 invoked by uid 10001); Thu, 30 Sep 2004 07:02:33 -0000 Date: Thu, 30 Sep 2004 19:02:32 +1200 From: Guy Thornley To: Mark Wong Cc: pgsql-performance@postgresql.org Subject: Re: O_DIRECT setting Message-ID: <20040930070232.GA8139@conker.esphion.com> Reply-To: Guy Thornley References: <20040920075734.GK21733@conker.esphion.com> <20040924080703.A27640@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040924080703.A27640@osdl.org> User-Agent: Mutt/1.5.5.1+cvs20040105i 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/334 X-Sequence-Number: 8462 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