To: Chris <csmith@squiz.net>
cc: pgsql-general@postgresql.org, pgsql-docs@postgresql.org
Subject: Re: [GENERAL] Re: user guide 
In-reply-to: <5.1.0.14.0.20010807090153.02e5a0a0@cooee.cybersydney.com.au> 
References: <Pine.LNX.4.21.0108060832400.11877-100000@theory.versive.org>
	<Pine.LNX.4.21.0108060832400.11877-100000@theory.versive.org>
	<5.1.0.14.0.20010807090153.02e5a0a0@cooee.cybersydney.com.au>
Comments: In-reply-to Chris <csmith@squiz.net>
	message dated "Tue, 07 Aug 2001 09:05:13 +1000"
Date: Mon, 06 Aug 2001 20:14:06 -0400
Message-ID: <26403.997143246@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Chris <csmith@squiz.net> writes:
>>> I have a suggestion, as well: I think the PostgreSQL documentatio could
>>> use a section that discusses all the maintenance issues in one place.
>> 
>> I agree.  Do I hear a volunteer to write it?

> I'd be interested in looking at it.
> Is it just this todo item : Add mention of VACUUM, log rotation to 
> Administrator's Guide ?

That was added as a result of the thread starting at
http://fts.postgresql.org/db/mw/msg.html?mid=115811

There are two things I think we need: one is a discussion of each of
these topics (which AFAIR are presently discussed nowhere); the other
is a short "checklist of maintenance concerns" that links to longer
discussions of each relevant topic.  For example, there's already a
discussion of backup methods, but it'd be good if that were listed in a
checklist of things for the budding admin to think about.

Or you could reorganize the Admin Guide so that backup and these other
things are sections in a Maintenance chapter.  Not sure if that'd be
better.

			regards, tom lane