pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: Where to document system views?
Date: Mon, 15 Oct 2001 15:31:23 -0400
Message-ID: <21289.1003174283@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0110152040370.631-100000@peter.localdomain>
References: <Pine.LNX.4.30.0110152040370.631-100000@peter.localdomain>

Peter Eisentraut <peter_e@gmx.net> writes:
> The pg_stat-related views ought to become part of a new section that
> describes that whole deal in the first place.  If there is a lot to say it
> could become a new chapter in the Admin Guide (perhaps "Monitoring...").

That seems like a good plan for Jan's runtime statistics stuff.  But
pg_stats doesn't quite fit with the others.  Maybe I'll put it into the
"performance tips" area.

> The others could become part of a chapter in the User's Guide I've been
> meaning to write on "schema creation", which would describe what tables,
> views, contraints, and such are.  A subsection on how to reverse engineer
> the created schema would fit naturally.

Seems okay.  Are you thinking of getting that done for 7.2, or is this a
long-term idea?

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <21289.1003174283@sss.pgh.pa.us>
Permalink:  ../21289.1003174283@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21289.1003174283@sss.pgh.pa.us

 · 

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: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net
  Subject: Re: Where to document system views?
  In-Reply-To: <21289.1003174283@sss.pgh.pa.us>

* 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