public inbox for [email protected]  
help / color / mirror / Atom feed
From: Jim C. Nasby <[email protected]>
To: Tom Lane <[email protected]>
Cc: Scott Marlowe <[email protected]>
Cc: [email protected]
Subject: Re: vacuum and routine maintenance docs
Date: Wed, 18 Jan 2006 19:14:22 -0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, Jan 18, 2006 at 07:55:07PM -0500, Tom Lane wrote:
> Scott Marlowe <[email protected]> writes:
> > Well, I'm kind of tempted to rewrite the whole section.  I'd like to
> > come up with some objectives of what we're trying to cover there, and
> > basically start over with all the information that's there plus the
> > other stuff on fsm and mvcc as it applies to vacuum, or link to it as
> > needed.
> 
> > To me, the docs feel kind of like they've evolved over time, so the
> > ordering and general layout feel klunky.  No slam on the folks who wrote
> > them to start with, or updated them.  Just makes my tech docs training
> > come out.
> 
> You're certainly right about the history of the docs, and I agree that a
> ground-up rewrite is the only thing that would help much --- trying to
> incorporate new separately-written material is just going to be "more of
> the same", ISTM, no matter how good that material might be on its own.
> 
> Is it reasonable to try to make an outline of how you think the chapter
> should go, or would that be premature without more discussion of
> objectives?

I'm wondering if people feel this is an issue with the docs in general
and isn't limited to just the admin stuff?

I know I certainly have trouble finding things... I generally look for
stuff by going to the appropriate page in the SQL syntax section and
seeing what it links too, but of course there's a lot of things that
aren't (and shouldn't be) linked to from there...
-- 
Jim C. Nasby, Sr. Engineering Consultant      [email protected]
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (23+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: vacuum and routine maintenance docs
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox