public inbox for [email protected]  
help / color / mirror / Atom feed
From: Neil Conway <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: Jim C. Nasby <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Scott Marlowe <[email protected]>
Cc: [email protected]
Subject: Re: vacuum and routine maintenance docs
Date: Thu, 19 Jan 2006 06:54:30 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, 2006-01-18 at 17:24 -0800, Joshua D. Drake wrote:
> Why is Managing Database and Routine Database Management separate?

I assume you mean the "Managing Databases" and "Routine Database
Maintenance Tasks" chapters. I think these chapters are separate because
they address fairly different subject matter. You could call the latter
chapter "Routine Maintenance Tasks" without loss of meaning, as it
doesn't focus on maintaining individual databases per se.

> Server configuration is kind of vague... Perhaps PostgreSQL 
> configuration?

Personally I don't think that's an improvement, although I'm not
completely satisfied with "Server Configuration" either.

> But then why isn't that under Managing Databases :)

Because that chapter describes managing individual databases and
tablespaces, not an entire PostgreSQL instance.

-Neil





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], [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