X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 97F909DC983 for ; Tue, 17 Jan 2006 13:31:46 -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 13446-05 for ; Tue, 17 Jan 2006 13:31:45 -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 627179DC99B for ; Tue, 17 Jan 2006 13:31:44 -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 17:31:43 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 17 Jan 2006 11:31:43 -0600 Subject: Re: Autovacuum / full vacuum From: Scott Marlowe To: Andrew Sullivan Cc: pgsql-performance@postgresql.org In-Reply-To: <20060117171656.GL21092@phlogiston.dyndns.org> References: <43CCC711.504@familyhealth.com.au> <20060117150800.GF21092@phlogiston.dyndns.org> <1137513565.25500.4.camel@state.g2switchworks.com> <20060117171656.GL21092@phlogiston.dyndns.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1137519102.25500.36.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 17 Jan 2006 11:31:43 -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/252 X-Sequence-Number: 16730 On Tue, 2006-01-17 at 11:16, Andrew Sullivan wrote: > On Tue, Jan 17, 2006 at 09:59:25AM -0600, Scott Marlowe wrote: > > I have to admit, looking at the documentation, that we really don't > > explain this all that well in the administration section, and I can see > > how easily led astray beginners are. > > I understand what you mean, but I suppose my reaction would be that > what we really need is a place to keep these things, with a note in > the docs that the "best practice" settings for these are documented > at , and evolve over time as people gain expertise with the > new features. > > I suspect, for instance, that nobody knows exactly the right settings > for any generic workload yet under 8.1 (although probably people know > them well enough for particular workloads). But the problem is bigger than that. The administrative docs were obviously evolved over time, and now they kind of jump around and around covering the same subject from different angles and at different depths. Even I find it hard to find what I need, and I know PostgreSQL administration well enough to be pretty darned good at it. For the beginner, it must seem much more confusing. The more I look at the administration section of the docs, the more I want to reorganize the whole thing, and rewrite large sections of it as well.