Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 6EF9E2E35F8 for ; Wed, 6 Feb 2008 12:12:47 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 24559-02 for ; Wed, 6 Feb 2008 12:12:42 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 2FD9A2E444F for ; Wed, 6 Feb 2008 12:12:41 -0400 (AST) Received: from perhan.alvh.no-ip.org (190-95-28-116.bk17-dsl.surnet.cl [190.95.28.116]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m16GCE6U022469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Feb 2008 08:12:57 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 66E1747BEC; Wed, 6 Feb 2008 13:12:02 -0300 (CLST) Date: Wed, 6 Feb 2008 13:12:02 -0300 From: Alvaro Herrera To: Adam Tauno Williams Cc: pgsql-admin Subject: Re: Where to find information on the new HOT tables? Message-ID: <20080206161202.GC17371@alvh.no-ip.org> References: <1d219a6f0802051142k882827cyd38ea7a3d7c1e4ea@mail.gmail.com> <1d219a6f0802051211o4814d979rdc988c2ad60b81d0@mail.gmail.com> <20080205202831.GF6483@alvh.no-ip.org> <200802052213.41185.dfontaine@hi-media.com> <28211.1202247311@sss.pgh.pa.us> <20080206154022.GB17371@alvh.no-ip.org> <1202314034.5753.28.camel@WM_ADAM1.morrison.iserv.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1202314034.5753.28.camel@WM_ADAM1.morrison.iserv.net> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 06 Feb 2008 08:12:57 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/62 X-Sequence-Number: 28136 Adam Tauno Williams escribió: > > > > I don't think such a document already exists, even rtfm_please doesn't know > > > > about any as of now. > > > The reason there isn't one is it doesn't need one; it's an > > > implementation detail not a user-visible feature. > > One reason to think it needs to be explained is that it affects how you > > plan for VACUUM. In tables where HOT is in charge of a large part of > > cleanup, you need to do a lot less vacuuming than you were for 8.2. In > > that sense it is very much user-visible. > > Wouldn't the thresholds in the auto-vaccuming make that adjustment > transparent? For people that use autovacuum, yes, it would, but not everybody does. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support