From: | momjian(at)postgresql(dot)org (Bruce Momjian - CVS) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/doc/src/sgml catalogs.sgml |
Date: | 2002-10-14 04:29:23 |
Message-ID: | 20021014042923.43ADA476241@postgresql.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: momjian(at)postgresql(dot)org 02/10/14 00:29:23
Modified files:
doc/src/sgml : catalogs.sgml
Log message:
- Link the entries in the table to the catalog heading
- Wrap them in the <database class="table"> tags, since thats what they
are (no markup rules for this, so it inherits from parent -- no style
change)
- Mention that pg_database, pg_shadow, and pg_group are global, and the
rest are local to the specific DB. (I believe this is correct).
> Works for me, though I suppose we could explain what the exceptions are
> like in general terms. Perhaps something like
>
> 'Most system catalogs are copied from the template database during
> database creation, and are thereafter database-specific. A few
> catalogs are physically shared across all databases in an installation;
> these are marked in the descriptions of the individual catalogs.'
Ok, new patch.
Rod Taylor
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-14 16:51:30 | pgsql-server/src backend/commands/copy.c backe ... |
Previous Message | Bruce Momjian - CVS | 2002-10-14 04:27:25 | pgsql-server/contrib/dbmirror README.dbmirror |