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 7CF733A4F4D for ; Sat, 22 Jan 2005 17:21:03 +0000 (GMT) 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 68530-07 for ; Sat, 22 Jan 2005 17:21:00 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id 475D03A4F3F for ; Sat, 22 Jan 2005 17:20:59 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1CsOwQ-0005Pl-00; Sat, 22 Jan 2005 12:20:54 -0500 To: Dawid Kuroczko Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <20050122.121300.41631131.t-ishii@sra.co.jp> <758d5e7f050122011713f9e27f@mail.gmail.com> <758d5e7f0501220518477cedfa@mail.gmail.com> In-Reply-To: <758d5e7f0501220518477cedfa@mail.gmail.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 22 Jan 2005 12:20:53 -0500 Message-ID: <87brbh753e.fsf@stark.xeocode.com> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.055 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/410 X-Sequence-Number: 10100 Dawid Kuroczko writes: > Quick thought -- would it be to possible to implement a 'partial VACUUM' > per analogiam to partial indexes? No. But it gave me another idea. Perhaps equally infeasible, but I don't see why. What if there were a map of modified pages. So every time any tuple was marked deleted it could be marked in the map as modified. VACUUM would only have to look at these pages. And if it could mark as free every tuple that was marked as deleted then it could unmark the page. The only downside I see is that this could be a source of contention on multi-processor machines running lots of concurrent update/deletes. -- greg