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 40C5C3A4FA3 for ; Sat, 22 Jan 2005 20:11: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 93047-02 for ; Sat, 22 Jan 2005 20:10:49 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by svr1.postgresql.org (Postfix) with ESMTP id B21443A4FCC for ; Sat, 22 Jan 2005 20:10:50 +0000 (GMT) Received: by flake.decibel.org (Postfix, from userid 1001) id B97E31C8FD; Sat, 22 Jan 2005 14:10:49 -0600 (CST) Date: Sat, 22 Jan 2005 14:10:49 -0600 From: "Jim C. Nasby" To: Greg Stark Cc: Dawid Kuroczko , pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering Message-ID: <20050122201049.GR67721@decibel.org> 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> <87brbh753e.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87brbh753e.fsf@stark.xeocode.com> X-Operating-System: FreeBSD 4.10-RELEASE-p3 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/413 X-Sequence-Number: 10103 From http://developer.postgresql.org/todo.php: Maintain a map of recently-expired rows This allows vacuum to reclaim free space without requiring a sequential scan On Sat, Jan 22, 2005 at 12:20:53PM -0500, Greg Stark wrote: > 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 > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"