Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 2DE569F97EE for ; Thu, 13 Sep 2007 13:40:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 81048-03 for ; Thu, 13 Sep 2007 13:39:56 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 2FF0E9F955E for ; Thu, 13 Sep 2007 13:39:56 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so459680ugf for ; Thu, 13 Sep 2007 09:39:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=qkiJZWCDSFX9jgZmR1Z2OH1s4yNGhZNd9dedbKIWbnI=; b=O7vmzjLNDvvL6R0LhgbTmIbrzoTiTaJz9cO4VnIPGgSrvqVoHwtw/heWvlxy8/joVmeAMW3bGmU/sVH3Ef/wPBRDApC2zx/H0IoQFuPgSBBZ4lhY/QXEJO/LnOrspQokN3fffGTdYQ4kii/QlU2B2Xn3uJzUgROpVD/ZNcUv/oM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GUGx7XEITgtMejgkPvR7J1h1OAd8+8F8h4Gy35fhiNxC7zIHrNGzSB7caaHHJFCvQn3frYdsAGV5/kKc/Rq5n3LVHfbjkQ5/T36QDYu7uHRy2p30J8CacR7ic4mpRDKgSrnUnohMqXC5NcQZSiTclNghDXQNMHidRta6xSu63BY= Received: by 10.67.21.11 with SMTP id y11mr3198030ugi.1189701595829; Thu, 13 Sep 2007 09:39:55 -0700 (PDT) Received: by 10.66.220.7 with HTTP; Thu, 13 Sep 2007 09:39:55 -0700 (PDT) Message-ID: Date: Thu, 13 Sep 2007 11:39:55 -0500 From: "Scott Marlowe" To: "Erik Jones" Subject: Re: [Again] Postgres performance problem Cc: "Greg Smith" , pgsql-performance@postgresql.org In-Reply-To: <81405E66-5110-4DA8-B315-D28EA124CDB6@myemma.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46E636CB.8080008@rentalia.com> <43393.192.121.104.48.1189495883.squirrel@zigo.dhs.org> <46E64891.9080005@rentalia.com> <20070911225242.GG38801@decibel.org> <46E79865.906@rentalia.com> <81405E66-5110-4DA8-B315-D28EA124CDB6@myemma.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/253 X-Sequence-Number: 26798 On 9/13/07, Erik Jones wrote: > On Sep 13, 2007, at 12:58 AM, Greg Smith wrote: > > > On Wed, 12 Sep 2007, Scott Marlowe wrote: > > > >> I'm getting more and more motivated to rewrite the vacuum docs. I > >> think a rewrite from the ground up might be best... I keep seeing > >> people doing vacuum full on this list and I'm thinking it's as > >> much because of the way the docs represent vacuum full as anything. > > > > I agree you shouldn't start thinking in terms of how to fix the > > existing documentation. I'd suggest instead writing a tutorial > > leading someone through what they need to know about their tables > > first and then going into how vacuum works based on that data. > > > > As an example, people throw around terms like "index bloat" and > > "dead tuples" when talking about vacuuming. The tutorial I'd like > > to see somebody write would start by explaining those terms and > > showing how to measure them--preferably with a good and bad example > > to contrast. The way these terms are thrown around right now, I > > don't expect newcomers to understand either the documentation or > > the advice people are giving them; I think it's shooting over their > > heads and what's needed are some walkthroughs. Another example I'd > > like to see thrown in there is what it looks like when you don't > > have enough FSM slots. > > Isn't that the point of the documentation? I mean, if the existing, > official manual has been demonstrated (through countless mailing list > help requests) to not sufficiently explain a given topic, shouldn't > it be revised? One thing that might help is a hyperlinked glossary > so that people reading through the documentation can go straight to > the postgres definition of dead tuple, index bloat, etc. Yes and no. The official docs are more of a technical specification. Short, simple and to the point so that if you know mostly what you're doing you don't have to wade through a long tutorial to find the answer. I find MySQL's documentation frustrating as hell because I can never find just the one thing I wanna look for. Because it's all written as a tutorial. I.e. I have to pay the "stupid tax" when I read their docs. What I want to do is two fold. 1: fix the technical docs so they have better explanations of each of the topics, without turning them into huge tutorials. 2: Write a vacuuming tutorial that will be useful should someone be new to postgresql and need to set up their system. I think the tutorial should be broken into at least two sections, a quick start guide and an ongoing maintenance and tuning section.