aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/bki.sgml22
-rw-r--r--doc/src/sgml/catalogs.sgml5
2 files changed, 14 insertions, 13 deletions
diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml
index 2e4b12f91b3..2b90f048e3b 100644
--- a/doc/src/sgml/bki.sgml
+++ b/doc/src/sgml/bki.sgml
@@ -1,4 +1,6 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.6 2000/12/23 16:24:29 petere Exp $ -->
+<!--
+$Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.7 2001/06/12 05:55:48 tgl Exp $
+ -->
<chapter id="bki">
<title><acronym>BKI</acronym> Backend Interface</title>
@@ -15,16 +17,14 @@
</para>
<para>
- <application>initdb</application> uses <acronym>BKI</acronym> files
+ <application>initdb</application> uses a <acronym>BKI</acronym> file
to do part of its job when creating a new database cluster. The
- input files used by <application>initbd</application> are created as
+ input file used by <application>initdb</application> is created as
part of building and installing <productname>Postgres</productname>
by a program named <filename>genbki.sh</filename> from some
specially formatted C header files in the source tree. The created
- BKI files are called <filename>global.bki</filename> (for global
- catalogs) and <filename>template1.bki</filename> (for the catalogs
- initially stored in the template1 database and then duplicated in
- every created database) and are normally installed in the
+ BKI file is called <filename>postgres.bki</filename> and is
+ normally installed in the
<filename>share</filename> subdirectory of the installation tree.
</para>
@@ -39,7 +39,7 @@
<para>
This section describes how the <productname>Postgres</productname>
backend interprets <acronym>BKI</acronym> files. This description
- will be easier to understand if the <filename>global.bki</filename>
+ will be easier to understand if the <filename>postgres.bki</filename>
file is at hand as an example. You should also study the source
code of <application>initdb</application> to get an idea of how the
backend is invoked.
@@ -49,7 +49,7 @@
BKI input consists of a sequence of commands. Commands are made up
of a number of tokens, depending on the syntax of the command.
Tokens are usually separated by whitespace, but need not be if
- there is no ambiguity. There is not special command separator; the
+ there is no ambiguity. There is no special command separator; the
next token that syntactically cannot belong to the preceeding
command starts a new one. (Usually you would put a new command on
a new line, for clarity.) Tokens can be certain key words, special
@@ -155,13 +155,13 @@
values and <replaceable
class="parameter">oid_value</replaceable> for its OID. If
<replaceable class="parameter">oid_value</replaceable> is zero
- (0) or the clause is ommitted, then the next available OID is
+ (0) or the clause is omitted, then the next available OID is
used.
</para>
<para>
NULL values can be specified using the special key word
- <literal>_null_</literal>. Values containing spaces should be
+ <literal>_null_</literal>. Values containing spaces must be
double quoted.
</para>
</listitem>
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 27b8314518a..9c3814820dc 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1,6 +1,6 @@
<!--
Documentation of the system catalogs, directed toward PostgreSQL developers
- $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.17 2001/05/14 20:30:19 momjian Exp $
+ $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.18 2001/06/12 05:55:48 tgl Exp $
-->
<chapter id="catalogs">
@@ -645,7 +645,8 @@
<entry>relisshared</entry>
<entry><type>bool</type></entry>
<entry></entry>
- <entry>XXX (This is not what it seems to be.)</entry>
+ <entry>True if this table is shared across all databases in the
+ cluster.</entry>
</row>
<row>