Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D47482E0254 for ; Thu, 7 Feb 2008 18:32:15 -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 38208-02-3 for ; Thu, 7 Feb 2008 18:32:11 -0400 (AST) Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id DA2412E02CA for ; Thu, 7 Feb 2008 18:31:42 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id m17MVBZ18035; Thu, 7 Feb 2008 17:31:11 -0500 (EST) From: Bruce Momjian Message-Id: <200802072231.m17MVBZ18035@momjian.us> Subject: Re: Where to find information on the new HOT tables? In-Reply-To: <200802072100.20093.dfontaine@hi-media.com> To: Dimitri Fontaine Date: Thu, 7 Feb 2008 17:31:11 -0500 (EST) CC: pgsql-admin@postgresql.org, Alvaro Herrera , Chris Hoover X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/81 X-Sequence-Number: 28155 Dimitri Fontaine wrote: -- Start of PGP signed section. > Le Thursday 07 February 2008 20:43:57 Bruce Momjian, vous avez ?crit?: > > Does the release note item on HOT need additions? > > If I put the release not item on HOT here: > > -=-=-=- > Heap-Only Tuples (HOT) accelerate space reuse for most UPDATEs and DELETEs > (Pavan Deolasee, with ideas from many others) > > UPDATEs and DELETEs leave dead tuples behind, as do failed INSERTs. Previously > only VACUUM could reclaim space taken by dead tuples. With HOT dead tuple > space can be reclaimed at the time of INSERT or UPDATE if no changes are made ^^^ > to indexed columns. This allows for more consistent performance. Also, HOT > avoids adding duplicate index entries. > -=-=-=- OK, what I did was to add the word "automatically" at the location indicated. Hopefully that will help. > I'd say it only misses the transparent & automatic precision, telling the > users they don't have anything to do about HOT: PostgreSQL is able on its own > to decide when HOT is or is not safe to use. > And I have to get it back that documentation is not verbose enough about how > HOT is working, just that you have to know where to look... > > What about Alvaro's concern about manual vacuuming policies editing wrt to > HOT? I think most people will be using autovacuum, and those who aren't will have to realize that HOT makes vacuuming less needed. -- Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +