X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 939799DC841 for ; Tue, 17 Jan 2006 18:59:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57216-03 for ; Tue, 17 Jan 2006 18:59:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 5BCAB9DC80F for ; Tue, 17 Jan 2006 18:59:27 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 17 Jan 2006 22:59:29 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 17 Jan 2006 16:59:29 -0600 Subject: Re: vacuum and routine maintenance docs From: Scott Marlowe To: "Jim C. Nasby" Cc: pgsql-docs@postgresql.org In-Reply-To: <20060117224941.GI17896@pervasive.com> References: <1137518049.25500.27.camel@state.g2switchworks.com> <20060117224941.GI17896@pervasive.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1137538769.25500.49.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 17 Jan 2006 16:59:29 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.119 required=5 tests=[AWL=0.118, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.119 X-Spam-Level: X-Archive-Number: 200601/28 X-Sequence-Number: 3418 Thanks. Yeah, I'm thinking more of a very brief mention of what the FSM is, with a link to the other part of the docs that discuss it. And then having a link (possibly in both places) or two to more in depth articles on fsm and fsm tuning. On Tue, 2006-01-17 at 16:49, Jim C. Nasby wrote: > Before you 'put pen to paper', I have two articles that you should look > at. One is on FSM, the other is more about MVCC from the standpoint of > why we use it and why it means needing to vacuum. I don't have the URL's > handy here, but I can post them tomorrow. > > On Tue, Jan 17, 2006 at 11:14:09AM -0600, Scott Marlowe wrote: > > After the most recent post on the general mailing list by someone who > > was a bit confused by postgresql's vacuuming and use of the free space > > map, I've been reviewing the page on routine maintenance. > > > > It's pretty obvious that this page was originally written for an older > > version of PostgreSQL and has had bits and pieces welded onto it over > > time to cover newer features, like the autovacuum daemon. > > > > I'd like to rewrite most of the page, or at least the parts referring to > > vacuuming and analyzing. They seem a bit scattered about on the page, > > and there's no mention at all of the free space map, something which is > > integral to vacuuming the database. > > > > So, before I go of slogging through the snow, a couple of questions. > > > > 1: Is there already a newer version in CVS? Should I check out the > > docs/src directory from there to start? Or can I just go on what's in > > the 8.1 release? > > > > 2: Any input on anyone as to what they feel they'd like to see in the > > docs for this section? > > > > The section on vacuuming and analysis seem kind of light on theory. I'm > > thinking we should mention something about the default statistics or at > > least a reference to a page that explains it. > > > > This also leads me to believe that what we cover on the > > runtime-config-resource page, because the coverage of the fsm there is > > kind of light too. > > > > So, any advice? > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 9: In versions below 8.0, the planner will ignore your desire to > > choose an index scan if your joining column's datatypes do not > > match > >