From: Greg Smith <gsmith@gregsmith.com>
To: pgsql-performance@postgresql.org
Subject: Re: [Again] Postgres performance problem
Date: Thu, 13 Sep 2007 01:58:10 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0709130130390.8547@westnet.com> (raw)
In-Reply-To: <dcc563d10709121128o1e5883a9n96b1f9ed74901be9@mail.gmail.com>
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>
<dcc563d10709121128o1e5883a9n96b1f9ed74901be9@mail.gmail.com>
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.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com
Subject: Re: [Again] Postgres performance problem
In-Reply-To: <Pine.GSO.4.64.0709130130390.8547@westnet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox