Skip site navigation (1) Skip section navigation (2)

Re: vacuum and routine maintenance docs

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)postgresql(dot)org
Subject: Re: vacuum and routine maintenance docs
Date: 2006-01-19 22:00:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On Thu, Jan 19, 2006 at 10:15:19AM -0600, Scott Marlowe wrote:
> I agree completely.  We don't probably need it in sgml just yet.  From a

Actually, I was looking for how to get the view out of the existing SGML
;) In any case, I think admin is probably broad enough that there won't
be much overlap with other sections.

> 40,000 ft perspective, we can break administration up into several large
> chunks, and then decide what needs to go in each.  The general "big
> topics" we already have seem pretty serviceable.  However, I tend to
> think of OS env and server config as being sub topics under
> installation.  Under that, we can put the individual subjects
> accordingly.
> - Installation
> -- Documentation scope specification
> -- Preparation (setting objectives for the installation)
> -- Hardware considerations (emphasizing things like fsyncing and all)
> -- OS configuration (i.e. shared memory)
> -- Software installation (source versus rpm versus pkg etc.)
> -- Cluster initialization (localization issues, location, etc...)
> -- Server configuration (i.e. pg_hba / postgresql.conf et. al.)
> -- Running the server (start up scripts, by hand, etc.)
> -- Verifying server operation (regression tests)

Should probably mention contrib in here somewhere... and other
resources, like pgFoundry. Afterall, the install section is somewhat of
someone's introduction to PostgreSQL...

> - Management
> -- Databases
> -- Users
> -- Roles and Privileges

Somewhere in one or both of the above should probably be some discussion
on security practices... Also, pg_hba.conf is a bit of a stickler,
because it is closely related to users and authentication.
postgresql.conf is also a bit tricky, because many of it's settings
require knowledge from other areas. Maybe the best way to deal with
these is extensive cross-linking? IE: each postgresql.conf item (or set
of items) should have a link back to whatever section explains it in
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to


pgsql-docs by date

Next:From: Scott MarloweDate: 2006-01-19 22:51:34
Subject: Re: vacuum and routine maintenance docs
Previous:From: Jim C. NasbyDate: 2006-01-19 21:51:48
Subject: Re: vacuum and routine maintenance docs

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group