Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 341302E456E for ; Wed, 6 Feb 2008 12:06:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 31551-01 for ; Wed, 6 Feb 2008 12:06:45 -0400 (AST) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by postgresql.org (Postfix) with ESMTP id 05BE12E4645 for ; Wed, 6 Feb 2008 12:06:20 -0400 (AST) Received: by py-out-1112.google.com with SMTP id d37so5175948pye.29 for ; Wed, 06 Feb 2008 08:06:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=+Wx1LLU7+mxNzoduGMqiiApxm8/kZ63o7ei/2i0vEys=; b=ZTckWldMy7Ux+kVwChyGZPmytcB329qnn89Rkd20gY1F9km3Sd19YbcekW7pFzIjIwuswybGLWkrn+zloqSACAs/leVQRvPjk/Ii6ko1tvDKEiRI0JS0EUOlvZdV+unyja2AU7j0vBTyFy3pvDfjCZ3Ndn6kTyFmp6MAB/mWw5U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=WbHdaC11Fv1ZGgc9Y+DcO9x8+9gX2UPUMpqqE3Io+svPXGOS1oCcZh23mvZCDTqStJmMBW42M+f4gd5Q27jSpqDxn/E6EEd3g9eVRQUjsZCLV/rmZ2skMN33tMFsfs83Arl+1oT5GRjuELv7HhILlA04PDpsKH7M1qGoxHUoC1k= Received: by 10.35.22.12 with SMTP id z12mr6697517pyi.42.1202313980228; Wed, 06 Feb 2008 08:06:20 -0800 (PST) Received: from ?192.168.1.212? ( [206.114.45.107]) by mx.google.com with ESMTPS id f77sm29122247pyh.32.2008.02.06.08.06.19 (version=SSLv3 cipher=RC4-MD5); Wed, 06 Feb 2008 08:06:19 -0800 (PST) Subject: Re: Where to find information on the new HOT tables? From: Adam Tauno Williams Reply-To: adamtaunowilliams@gmail.com To: pgsql-admin In-Reply-To: <20080206154022.GB17371@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> Content-Type: text/plain Date: Wed, 06 Feb 2008 11:07:14 -0500 Message-Id: <1202314034.5753.28.camel@WM_ADAM1.morrison.iserv.net> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/61 X-Sequence-Number: 28135 > > > 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?