Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 8FE5B2E1891 for ; Thu, 7 Feb 2008 16:00:31 -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 06258-03 for ; Thu, 7 Feb 2008 16:00:28 -0400 (AST) Received: from hi-media.com (9.140-14-84.ripe.coltfrance.com [84.14.140.9]) by postgresql.org (Postfix) with ESMTP id E6ABC2E420A for ; Thu, 7 Feb 2008 16:00:27 -0400 (AST) Received: from dalistar.local (cac94-7-82-243-27-82.fbx.proxad.net [82.243.27.82]) by hi-media.com (Postfix) with ESMTP id 7DB2E1D0275; Thu, 7 Feb 2008 20:57:57 +0100 (CET) From: Dimitri Fontaine To: Bruce Momjian Subject: Re: Where to find information on the new HOT tables? Date: Thu, 7 Feb 2008 21:00:17 +0100 User-Agent: KMail/1.9.7 Cc: pgsql-admin@postgresql.org, Alvaro Herrera , Chris Hoover References: <200802071943.m17Jhva22531@momjian.us> In-Reply-To: <200802071943.m17Jhva22531@momjian.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2357239.liu2zKuPnF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802072100.20093.dfontaine@hi-media.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/80 X-Sequence-Number: 28154 --nextPart2357239.liu2zKuPnF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le Thursday 07 February 2008 20:43:57 Bruce Momjian, vous avez =E9crit=A0: > Does the release note item on HOT need additions? If I put the release not item on HOT here: =2D=3D-=3D-=3D- Heap-Only Tuples (HOT) accelerate space reuse for most UPDATEs and DELETEs= =20 (Pavan Deolasee, with ideas from many others)=20 UPDATEs and DELETEs leave dead tuples behind, as do failed INSERTs. Previou= sly=20 only VACUUM could reclaim space taken by dead tuples. With HOT dead tuple=20 space can be reclaimed at the time of INSERT or UPDATE if no changes are ma= de=20 to indexed columns. This allows for more consistent performance. Also, HOT= =20 avoids adding duplicate index entries. =2D=3D-=3D-=3D- I'd say it only misses the transparent & automatic precision, telling the=20 users they don't have anything to do about HOT: PostgreSQL is able on its o= wn=20 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 ho= w=20 HOT is working, just that you have to know where to look... What about Alvaro's concern about manual vacuuming policies editing wrt to= =20 HOT? Regards, =2D-=20 dim --nextPart2357239.liu2zKuPnF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHq2NUlBXRlnbh1bkRAnCwAJ9Vv2n0X/Lne+ffjdg6St2NYFvK2wCffKe5 ZJUfqjPOE4pNc+8Pw5/EG3g= =6Yd+ -----END PGP SIGNATURE----- --nextPart2357239.liu2zKuPnF--