Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 341B82E3AC6 for ; Wed, 6 Feb 2008 05:39:45 -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 59456-03-3 for ; Wed, 6 Feb 2008 05:39:34 -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 DF79F2E3E72 for ; Wed, 6 Feb 2008 05:11:16 -0400 (AST) Received: from dim (gut75-1-81-57-27-121.fbx.proxad.net [81.57.27.121]) by hi-media.com (Postfix) with ESMTP id 6371618807A; Wed, 6 Feb 2008 10:08:47 +0100 (CET) From: Dimitri Fontaine Organization: Hi-Media To: Tom Lane Subject: Re: Where to find information on the new HOT tables? Date: Wed, 6 Feb 2008 10:11:09 +0100 User-Agent: KMail/1.9.7 Cc: "Jonah H. Harris" , Decibel! , "Joshua D. Drake" , pgsql-admin@postgresql.org, "Alvaro Herrera" , "Chris Hoover" , "Bruce Momjian" References: <1d219a6f0802051142k882827cyd38ea7a3d7c1e4ea@mail.gmail.com> <36e682920802052145lc3b566cr1facc1cd76847a5a@mail.gmail.com> <2827.1202278590@sss.pgh.pa.us> In-Reply-To: <2827.1202278590@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6573818.E74r5SsFfP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802061011.11929.dfontaine@hi-media.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/53 X-Sequence-Number: 28127 --nextPart6573818.E74r5SsFfP Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Le mercredi 06 f=C3=A9vrier 2008, Tom Lane a =C3=A9crit=C2=A0: > I'm really not seeing the case for user-level documentation of HOT, > when for instance most of the planner's optimization behavior is not > so documented. In my POV, the case for HOT to appear in the documentation as been made by = the=20 PR and Presskit. They both announce HOT to be a major performance addition = in=20 8.3 that users will want to benefit from. Now we have to tell some more to= =20 the users, I think we want to answer those two basic questions:=20 - How do I check that I'm using HOT? (you don't, transparent feature, blah) - What's HOT is so good about compared to how PostgreSQL used to work? My proposal was about answering this without requiring the user to be capab= le=20 of understanding internals and 'developer topics'. If you want me to talk about another documentation missing entry, I'll be=20 happy to request a user targetted presentation of Executor Nodes, their inp= ut=20 and output, relative costs (simplified algorithms?) and the reason behind=20 their choice by the planner. I'm slowly becoming familiar with their names,= a=20 little more each time I Explain [Analyze] a query, but not enough so to yet= =20 be able to sketch an article about this... I'd also like to add that people judging documentation effectiveness by its= =20 length are certainly not real users of it. I've yet to meet a PostgreSQL us= er=20 who doesn't praise the product documentation, even if newcomers often need= =20 some time to be able to understand where to find what. The Tsearch enabled= =20 website has been a huge improvement here. To ease PostgreSQL newbies manual grasping, I certainly don't think it will= =20 need shortening the documentation. Once more, all of this is only a enthusiastic user POV, the kind who think= =20 he's helping when writing this mail ;) =2D-=20 dim --nextPart6573818.E74r5SsFfP 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) iD8DBQBHqXmvlBXRlnbh1bkRAjQZAKCWJaRGPSngnrZKBKtojZKSCZKxXACgqa6l CmRmExmAPKdWZzIfhfDvc5E= =zQb/ -----END PGP SIGNATURE----- --nextPart6573818.E74r5SsFfP--