Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 9266F2E3EAC for ; Wed, 6 Feb 2008 03:17:04 -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 30493-03 for ; Wed, 6 Feb 2008 03:17:00 -0400 (AST) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by postgresql.org (Postfix) with ESMTP id A426B2E3EB5 for ; Wed, 6 Feb 2008 03:17:00 -0400 (AST) Received: by rv-out-0910.google.com with SMTP id g13so2058243rvb.43 for ; Tue, 05 Feb 2008 23:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=wV6U2uXboe5thtM40GUUol3dwKR792qGBFaEAfHK/LU=; b=t0BfFCvQQj+yNFUths4f50Ol4KMic/GiSm5NXqCIXI98G66YnMRVsrZKBkX6lSUfyE+OwYrBbbYnA8X7VuO3SpkIb+P/eVnZ4mkAVNXlq/rzksXFqgEeHkwRxidJo9TDSbXjR4RlmOPwaZnH9G72+J3FIDNARb0uh4w4iekpZjA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pc+H6/g6vsvvyS3FpJ6WXkAo9+27ANIRrdliCSqeP5qIsnJXZwoKm3COYBZIMs13gabyzbONErbPqMcc0yzpAF2nZqqbyW/ZLRjG2newGQP6hOv6BGOXeyLXjoMq48dwQr63RMEJ7N75XuVMPjB6MLTaA0W20vRJTvcwgpFUG54= Received: by 10.141.83.15 with SMTP id k15mr6378414rvl.120.1202282219478; Tue, 05 Feb 2008 23:16:59 -0800 (PST) Received: by 10.141.169.5 with HTTP; Tue, 5 Feb 2008 23:16:59 -0800 (PST) Message-ID: <684362e10802052316w50d34c0n20262dfef4f7a06c@mail.gmail.com> Date: Wed, 6 Feb 2008 13:16:59 +0600 From: "Markus Bertheau" To: "Tom Lane" Subject: Re: Where to find information on the new HOT tables? Cc: "Jonah H. Harris" , Decibel! , "Joshua D. Drake" , "Dimitri Fontaine" , pgsql-admin@postgresql.org, "Alvaro Herrera" , "Chris Hoover" , "Bruce Momjian" In-Reply-To: <2827.1202278590@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1d219a6f0802051142k882827cyd38ea7a3d7c1e4ea@mail.gmail.com> <28211.1202247311@sss.pgh.pa.us> <200802052314.02679.dfontaine@hi-media.com> <20080205142535.12e5c28e@jd-laptop> <29236.1202252251@sss.pgh.pa.us> <20080206015351.GM1212@decibel.org> <1250.1202267491@sss.pgh.pa.us> <20080206045406.GP1212@decibel.org> <36e682920802052145lc3b566cr1facc1cd76847a5a@mail.gmail.com> <2827.1202278590@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/51 X-Sequence-Number: 28125 2008/2/6, Tom Lane : > 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. Actually that would be very useful information. Questions like how is cost calculated, how are joins ordered, which kinds of subselects are pulled up to the outer query and so on are quite essential when optimizing queries and understanding query plans. Also more detailed information on how to tune the various performance parameters for bg_writer, autovacuum, checkpointing and so on would be useful in my opinion. I find the current manual very useful and the fact that it's 2000 pages doesn't make it any less useful. Markus