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 F3DFA3A5154 for ; Sun, 23 Jan 2005 06:51:39 +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 84781-04 for ; Sun, 23 Jan 2005 06:51:22 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 347883A50AC for ; Sun, 23 Jan 2005 06:50:18 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 91C9E31D92; Sun, 23 Jan 2005 07:50:17 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.performance Subject: Cheaper VACUUMing Date: Sun, 23 Jan 2005 01:16:20 -0500 Organization: cbbrowne Computing Inc Lines: 33 Message-ID: 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 X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Corporate Culture, linux) Cancel-Lock: sha1:GqW+uK6OKCOcjKFLQnETvgLdwqM= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.093 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/420 X-Sequence-Number: 10110 A long time ago, in a galaxy far, far away, gsstark@mit.edu (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. I was thinking the same thing after hearing fairly extensive "pooh-poohing" of the notion of vacuuming based on all the pages in the shared cache. This "hot list page table" would probably need to be a hash table. It rather parallels the FSM, including the way that it would need to be limited in size. -- wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','gmail.com'). http://cbbrowne.com/info/lsf.html Rules of the Evil Overlord #57. "Before employing any captured artifacts or machinery, I will carefully read the owner's manual."