From: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: [Again] Postgres performance problem
Date: Fri, 14 Sep 2007 03:19:51 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0709131059340.4400@westnet.com> (raw)
In-Reply-To: <dcc563d10709130729oc290afbi89b31aa4c206679f@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>
<Pine.GSO.4.64.0709130130390.8547@westnet.com>
<dcc563d10709130729oc290afbi89b31aa4c206679f@mail.gmail.com>
On Thu, 13 Sep 2007, Scott Marlowe wrote:
> I think both things are needed actually. The current docs were
> started back when pg 7.2 roamed the land, and they've been updated a
> bit at a time...
No argument here that ultimately the documentation needs to be updated as
well. I was just suggesting what I've been thinking about as the path of
least resistance to move in that direction. Updating the documentation is
harder to do because of the build process involved. It's easier to write
something new that addresses the deficiencies, get that right, and then
merge it into the documentation when it's stable. After the main new
content is done, then it's easier to sweep back through the existing
material and clean things up.
> Which leads me to thinking that we then need a simple tutorial on
> vacuuming to include the free space map, vacuum, vacuum analyze,
> vacuum full, and the autovacuum daemon.
Right, that's the sort of thing that's missing right now, and I think that
would be more useful to newbies than correcting the documentation that's
already there.
Also: if you don't have a public working area to assemble this document
at, I've set a precedent of sorts that it's OK to put working material
like this onto the PG developer's wiki at http://developer.postgresql.org/
as long as your stated intention is ultimately to move it off of there
once it's complete. In addition to providing a nice set of tools for
working the text (presuming you're comfortable with Wiki syntax) that will
get you a pool of reviewers/contributors who can make changes directly
rather than you needing to do all the work yourself.
--
* 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.0709131059340.4400@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