Avoid using the terms 'installation', 'site', or 'instance' when referring
to the thing you get from running initdb. That's called a database cluster (per SQL).
This commit is contained in:
parent
046848c272
commit
387d43113c
@ -34,9 +34,9 @@
|
||||
<Para>
|
||||
A single <Application>postmaster</Application> manages a given collection of
|
||||
databases on a single host. Such a collection of
|
||||
databases is called an installation or site. Frontend
|
||||
databases is called a cluster (of databases). Frontend
|
||||
applications that wish to access a given database
|
||||
within an installation make calls to the library.
|
||||
within a cluster make calls to the library.
|
||||
The library sends user requests over the network to the
|
||||
<Application>postmaster</Application>
|
||||
(<XRef LinkEnd="PGARCH-CONNECTIONS" EndTerm="PGARCH-CONNECTIONS">(a)),
|
||||
|
@ -35,9 +35,9 @@
|
||||
<Para>
|
||||
A single <Application>postmaster</Application> manages a given collection of
|
||||
databases on a single host. Such a collection of
|
||||
databases is called an installation or site. Frontend
|
||||
databases is called a cluster (of databases). Frontend
|
||||
applications that wish to access a given database
|
||||
within an installation make calls to the library.
|
||||
within a cluster make calls to the library.
|
||||
The library sends user requests over the network to the
|
||||
<Application>postmaster</Application> (<XRef LinkEnd="ARCH-CLIENTSERVER" EndTerm="ARCH-CLIENTSERVER">),
|
||||
which in turn starts a new backend server process
|
||||
|
@ -1,22 +1,10 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.11 2000/12/21 22:55:27 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.12 2000/12/22 19:31:56 petere Exp $
|
||||
-->
|
||||
|
||||
<sect1 id="terminology">
|
||||
<title>Terminology</title>
|
||||
|
||||
<para>
|
||||
In the following documentation,
|
||||
<firstterm>site</firstterm>
|
||||
may be interpreted as the host machine on which
|
||||
<Productname>Postgres</Productname> is installed.
|
||||
Since it is possible to install more than one set of
|
||||
<Productname>Postgres</Productname>
|
||||
databases on a single host, this term more precisely denotes any
|
||||
particular set of installed
|
||||
<Productname>Postgres</Productname> binaries and databases.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The
|
||||
<Productname>Postgres</Productname> <firstterm>superuser</firstterm>
|
||||
|
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.15 2000/12/22 18:57:50 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.16 2000/12/22 19:31:56 petere Exp $
|
||||
-->
|
||||
|
||||
<chapter id="query">
|
||||
@ -88,8 +88,8 @@ mydb=> \i basics.sql
|
||||
are <firstterm>attributes</firstterm>.
|
||||
As previously discussed, classes are grouped into
|
||||
databases, and a collection of databases managed by a
|
||||
single <application>postmaster</application> process constitutes an installation
|
||||
or site.
|
||||
single <application>postmaster</application> process constitutes a
|
||||
database cluster.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user